CVE-2026-74901

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) 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 — 3 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 an authentication bypass vulnerability in pqc.py where AES-GCM decryption failures trigger fallback to unauthenticated AES-CTR mode. Attackers can modify ciphertext in transit to bypass integrity verification and perform bit-flipping attacks without detection.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github.
generic

openssl_encrypt before 1.4.0 Authentication Bypass via AES-CTR Fallback | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-authentication-bypass-via-aes-ctr-fallback
github Patch Available

PQC fallback to unauthenticated AES-CTR when GCM fails · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-w4j7-wfgw-r52w

Vendor Advisories for CVE-2026-74901(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.0b8 (44 versions)1.4.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 51× in last 7d / 209× 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.

Showing the most recent 100 of 235 total refreshes for this CVE.

  1. 2026-09-19 07:12 UTCGHSA enrichment
  2. 2026-09-19 03:01 UTCGHSA enrichment
  3. 2026-09-18 22:52 UTCEG score recompute
  4. 2026-09-18 22:52 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 18:45 UTCGHSA enrichment
  7. 2026-09-18 14:27 UTCGHSA enrichment
  8. 2026-09-18 10:19 UTCGHSA enrichment
  9. 2026-09-18 06:11 UTCGHSA enrichment
  10. 2026-09-18 02:04 UTCGHSA enrichment
  11. 2026-09-17 21:56 UTCEG score recompute
  12. 2026-09-17 21:56 UTCGHSA enrichment
  13. 2026-09-17 16:08 UTCGHSA enrichment
  14. 2026-09-17 12:00 UTCGHSA enrichment
  15. 2026-09-17 07:52 UTCGHSA enrichment
  16. 2026-09-17 03:44 UTCGHSA enrichment
  17. 2026-09-16 23:10 UTCGHSA enrichment
  18. 2026-09-16 15:17 UTCEG score recompute
  19. 2026-09-16 15:17 UTCGHSA enrichment
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 10:15 UTCGHSA enrichment
  22. 2026-09-16 05:43 UTCEG score recompute
  23. 2026-09-16 05:43 UTCGHSA enrichment
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-16 01:36 UTCGHSA enrichment
Show 75 more
  1. 2026-09-15 21:28 UTCGHSA enrichment
  2. 2026-09-15 17:06 UTCGHSA enrichment
  3. 2026-09-15 12:58 UTCGHSA enrichment
  4. 2026-09-15 08:27 UTCGHSA enrichment
  5. 2026-09-15 04:18 UTCEG score recompute
  6. 2026-09-15 04:18 UTCGHSA enrichment
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-15 00:10 UTCGHSA enrichment
  9. 2026-09-14 19:56 UTCGHSA enrichment
  10. 2026-09-14 14:16 UTCGHSA enrichment
  11. 2026-09-14 10:08 UTCGHSA enrichment
  12. 2026-09-14 05:35 UTCGHSA enrichment
  13. 2026-09-14 01:27 UTCGHSA enrichment
  14. 2026-09-13 21:20 UTCGHSA enrichment
  15. 2026-09-13 17:11 UTCEG score recompute
  16. 2026-09-13 17:11 UTCGHSA enrichment
  17. 2026-09-13 13:03 UTCGHSA enrichment
  18. 2026-09-13 08:55 UTCGHSA enrichment
  19. 2026-09-13 04:48 UTCGHSA enrichment
  20. 2026-09-13 00:40 UTCGHSA enrichment
  21. 2026-09-12 20:27 UTCGHSA enrichment
  22. 2026-09-12 16:19 UTCEG score recompute
  23. 2026-09-12 16:19 UTCGHSA enrichment
  24. 2026-09-12 15:02 UTCEPSS rescore
  25. 2026-09-12 12:12 UTCGHSA enrichment
  26. 2026-09-12 08:03 UTCGHSA enrichment
  27. 2026-09-12 03:55 UTCGHSA enrichment
  28. 2026-09-11 23:47 UTCGHSA enrichment
  29. 2026-09-11 19:19 UTCGHSA enrichment
  30. 2026-09-11 15:12 UTCEG score recompute
  31. 2026-09-11 15:12 UTCGHSA enrichment
  32. 2026-09-11 14:53 UTCEPSS rescore
  33. 2026-09-11 11:04 UTCEG score recompute
  34. 2026-09-11 11:04 UTCGHSA enrichment
  35. 2026-09-11 06:22 UTCGHSA enrichment
  36. 2026-09-11 02:14 UTCGHSA enrichment
  37. 2026-09-10 22:06 UTCGHSA enrichment
  38. 2026-09-10 17:58 UTCGHSA enrichment
  39. 2026-09-10 13:50 UTCGHSA enrichment
  40. 2026-09-10 09:42 UTCEG score recompute
  41. 2026-09-10 09:42 UTCGHSA enrichment
  42. 2026-09-10 09:35 UTCEPSS rescore
  43. 2026-09-10 05:23 UTCGHSA enrichment
  44. 2026-09-10 01:15 UTCGHSA enrichment
  45. 2026-09-09 17:17 UTCGHSA enrichment
  46. 2026-09-09 11:57 UTCGHSA enrichment
  47. 2026-09-09 07:49 UTCGHSA enrichment
  48. 2026-09-09 03:42 UTCEG score recompute
  49. 2026-09-09 03:42 UTCGHSA enrichment
  50. 2026-09-08 22:01 UTCEPSS rescore
  51. 2026-09-08 04:34 UTCGHSA enrichment
  52. 2026-09-08 00:27 UTCGHSA enrichment
  53. 2026-09-07 20:19 UTCGHSA enrichment
  54. 2026-09-07 16:11 UTCEG score recompute
  55. 2026-09-07 16:11 UTCGHSA enrichment
  56. 2026-09-07 10:40 UTCGHSA enrichment
  57. 2026-09-07 04:44 UTCGHSA enrichment
  58. 2026-09-06 21:55 UTCGHSA enrichment
  59. 2026-09-06 17:44 UTCEG score recompute
  60. 2026-09-06 17:44 UTCGHSA enrichment
  61. 2026-09-06 13:48 UTCEPSS rescore
  62. 2026-09-06 13:36 UTCGHSA enrichment
  63. 2026-09-06 09:28 UTCGHSA enrichment
  64. 2026-09-06 05:20 UTCGHSA enrichment
  65. 2026-09-06 01:13 UTCGHSA enrichment
  66. 2026-09-05 20:52 UTCGHSA enrichment
  67. 2026-09-05 16:44 UTCEG score recompute
  68. 2026-09-05 16:44 UTCGHSA enrichment
  69. 2026-09-05 12:37 UTCGHSA enrichment
  70. 2026-09-05 08:29 UTCGHSA enrichment
  71. 2026-09-05 04:21 UTCGHSA enrichment
  72. 2026-09-05 00:14 UTCGHSA enrichment
  73. 2026-09-04 19:04 UTCGHSA enrichment
  74. 2026-09-04 14:08 UTCEG score recompute
  75. 2026-09-04 14:08 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-74901?
CVE-2026-74901 is a critical vulnerability published on August 17, 2026. openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption failures trigger fallback to unauthenticated AES-CTR mode. Attackers can modify ciphertext in transit to bypass integrity verification and perform bit-flipping attacks without…
When was CVE-2026-74901 disclosed?
CVE-2026-74901 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74901 actively exploited?
CVE-2026-74901 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 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-74901?
CVE-2026-74901 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74901?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74901, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74901

Explore →

Is Your Infrastructure Affected by CVE-2026-74901?

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

Start Free Scan →Browse All CVEs