openssl_encrypt versions before 1.4.0 contain an information disclosure vulnerability in the /ready endpoint that returns full database exception strings to unauthenticated callers. Attackers can trigger database errors to extract sensitive information including hostnames, IP addresses, connection parameters, and potentially credentials from exception messages.
CVE-2026-74879
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026openssl_encrypt before 1.4.0 Information Disclosure via /ready endpoint | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-information-disclosure-via-ready-endpointReadiness endpoint leaks database error details to unauthenticated callers · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-2vhw-q7vh-7xv2Vendor Advisories for CVE-2026-74879(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 06:06 UTCEG score recompute
- 2026-08-21 06:06 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:10 UTCGHSA enrichment
- 2026-08-20 06:14 UTCGHSA enrichment
- 2026-08-19 18:17 UTCEG score recompute
- 2026-08-19 18:17 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 04:55 UTCGHSA enrichment
- 2026-08-18 16:59 UTCEG score recompute
- 2026-08-18 16:59 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 04:20 UTCGHSA enrichment
- 2026-08-17 16:23 UTCEG score recompute
- 2026-08-17 16:23 UTCGHSA enrichment
- 2026-08-17 11:39 UTCEG score recompute
- 2026-08-17 11:13 UTCEG score recompute
- 2026-08-17 11:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-209
Frequently asked(5)
What is CVE-2026-74879?
When was CVE-2026-74879 disclosed?
Is CVE-2026-74879 actively exploited?
What is the CVSS score of CVE-2026-74879?
How do I remediate CVE-2026-74879?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74879
Is Your Infrastructure Affected by CVE-2026-74879?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.