CVE-2026-74891

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

openssl_encrypt versions before 1.4.0 contain hardcoded database credentials in standalone server configuration files. Attackers on the same network can access PostgreSQL databases using well-known default credentials to retrieve sensitive data.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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 computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available. Sources: github.
generic

openssl_encrypt before 1.4.0 Hardcoded Database Credentials | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-hardcoded-database-credentials
github Patch Available

Hardcoded database credentials in standalone servers · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-v4vm-4xf2-fhqj

Vendor Advisories for CVE-2026-74891(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 38× in last 7d / 38× 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.

  1. 2026-08-21 05:19 UTCGHSA enrichment
  2. 2026-08-21 01:29 UTCEG score recompute
  3. 2026-08-21 01:29 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:40 UTCGHSA enrichment
  6. 2026-08-20 17:51 UTCGHSA enrichment
  7. 2026-08-20 14:01 UTCGHSA enrichment
  8. 2026-08-20 09:41 UTCGHSA enrichment
  9. 2026-08-20 05:52 UTCGHSA enrichment
  10. 2026-08-20 02:03 UTCGHSA enrichment
  11. 2026-08-19 22:14 UTCGHSA enrichment
  12. 2026-08-19 18:25 UTCEG score recompute
  13. 2026-08-19 18:25 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:36 UTCGHSA enrichment
  16. 2026-08-19 10:47 UTCGHSA enrichment
  17. 2026-08-19 06:57 UTCGHSA enrichment
  18. 2026-08-19 03:08 UTCGHSA enrichment
  19. 2026-08-18 23:15 UTCGHSA enrichment
  20. 2026-08-18 19:25 UTCGHSA enrichment
  21. 2026-08-18 15:35 UTCEG score recompute
  22. 2026-08-18 15:35 UTCGHSA enrichment
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 11:32 UTCGHSA enrichment
Show 13 more
  1. 2026-08-18 07:43 UTCGHSA enrichment
  2. 2026-08-18 03:52 UTCGHSA enrichment
  3. 2026-08-18 00:02 UTCGHSA enrichment
  4. 2026-08-17 20:12 UTCGHSA enrichment
  5. 2026-08-17 16:23 UTCEG score recompute
  6. 2026-08-17 16:23 UTCGHSA enrichment
  7. 2026-08-17 16:10 UTCEG score recompute
  8. 2026-08-17 16:10 UTCGHSA enrichment
  9. 2026-08-17 15:28 UTCEG score recompute
  10. 2026-08-17 15:28 UTCGHSA enrichment
  11. 2026-08-17 11:39 UTCEG score recompute
  12. 2026-08-17 11:13 UTCEG score recompute
  13. 2026-08-17 11:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-74891?
CVE-2026-74891 is a critical vulnerability published on August 17, 2026. openssl_encrypt versions before 1.4.0 contain hardcoded database credentials in standalone server configuration files. Attackers on the same network can access PostgreSQL databases using well-known default credentials to retrieve sensitive data.
When was CVE-2026-74891 disclosed?
CVE-2026-74891 was first published in the National Vulnerability Database on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74891 actively exploited?
CVE-2026-74891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74891?
CVE-2026-74891 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74891?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74891, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74891

Explore →

Is Your Infrastructure Affected by CVE-2026-74891?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs