Information disclosure via verbose ready errors
Published Aug 17, 2026 · Updated Aug 17, 2026
Information disclosure in OpenSSL Encrypt before 1.4.0 allows remote attackers to read internal database details via the /ready endpoint. In openssl_encrypt_server/server.py, the readiness handler catches database exceptions and returns str(e) in the JSON reason field instead of a generic failure message. No authentication is required; anyone who can reach the service can trigger database errors and harvest hostnames, IP addresses, connection parameters, driver data, and sometimes credentials echoed by the backend.
Summary
What happened
Information disclosure in OpenSSL Encrypt before 1.4.0 allows remote attackers to read internal database details via the /ready endpoint. In openssl_encrypt_server/server.py, the readiness handler catches database exceptions and returns str(e) in the JSON reason field instead of a generic failure message. No authentication is required; anyone who can reach the service can trigger database errors and harvest hostnames, IP addresses, connection parameters, driver data, and sometimes credentials echoed by the backend.
The record
- CVE
- CVE-2026-74879
- Published
- Aug 17, 2026
- Updated
- Aug 17, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-209
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.4.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo