CVE-2026-75803

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
9.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function.

Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages.

CWE: CWE-354 (Improper Validation of Integrity Check Value)

Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case.

FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.

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

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
https://openssl-library.org/news/secadv/20260825.txt
github_commit

commit bf95f5f772e9 (openssl/openssl)

Fix landed in openssl/openssl commit bf95f5f772e9 — awaiting tagged release

https://github.com/openssl/openssl/commit/bf95f5f772e9362f87b25cfa2f8cb15d984865b9
github_commit

commit bdeb0cd994d9 (openssl/openssl)

Fix landed in openssl/openssl commit bdeb0cd994d9 — awaiting tagged release

https://github.com/openssl/openssl/commit/bdeb0cd994d915342787f117ee75044f0dc36f34
github_commit

commit 6c7aa6f8f644 (openssl/openssl)

Fix landed in openssl/openssl commit 6c7aa6f8f644 — awaiting tagged release

https://github.com/openssl/openssl/commit/6c7aa6f8f6449b7fe0137ee8be65fcd239bd7d6a
github_commit

commit 3621257986e2 (openssl/openssl)

Fix landed in openssl/openssl commit 3621257986e2 — awaiting tagged release

https://github.com/openssl/openssl/commit/3621257986e27e540bf96a11570929a6e5a9e05b
github_commit

commit 119ab9555dc6 (openssl/openssl)

Fix landed in openssl/openssl commit 119ab9555dc6 — awaiting tagged release

https://github.com/openssl/openssl/commit/119ab9555dc62275bbd71f6f49529b1a44feba42

Vendor Advisories for CVE-2026-75803(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.5) @ resolute2026-09-19ubuntu
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-09-19ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 4.0.2-1 (86 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.7-1~deb13u1 (13 versions)3.5.7-1~deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 4.0.2-1 (28 versions)——

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 88× in last 7d / 241× 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 241 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-75803?
CVE-2026-75803 is a critical vulnerability published on August 25, 2026. Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and…
When was CVE-2026-75803 disclosed?
CVE-2026-75803 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75803 actively exploited?
CVE-2026-75803 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 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-75803?
CVE-2026-75803 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-75803?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75803, 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-75803

Explore →

Is Your Infrastructure Affected by CVE-2026-75803?

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

Start Free Scan →Browse All CVEs