CVE-2026-75803

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM 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.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
Patch available. 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(9)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl (3.0.13-0ubuntu3.15) @ noble2026-10-10ubuntu
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.5) @ resolute2026-10-10ubuntu
ubuntuqemu-efi-arm (0~20180205.c0d9813c-2ubuntu0.3+esm3) @ bionic2026-10-10ubuntu
redhatruby3-3-main-3.3.10-23.6.hum12026-09-02redhat
redhatruby3-4-main-3.4.10-31.7.hum12026-09-02redhat
redhatruby4-0-main-4.0.6-37.3.hum12026-09-02redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl-main-3.5.8-0.1.hum12026-08-25redhat
redhatrust-bootupd-main-0.2.36-3.hum12026-08-25redhat
redhatpython-cryptography-main-50.0.0-1.hum12026-08-17redhat
redhatchunkah-main-0.6.0-3.hum12026-07-21redhat

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

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.3.7-r1: fixed in 3.3.7-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.5.8-r0: fixed in 3.5.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.5.8-r0: fixed in 3.5.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.5.8-r0: fixed in 3.5.8-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.0.10-1 ... 3.0.9-1 (23 versions)
  • every version up to 3.0.22-1~deb12u1: fixed in 3.0.22-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.5.7-1~deb13u1 (13 versions)
  • every version up to 3.5.7-1~deb13u2: fixed in 3.5.7-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.6.3-1 (23 versions)
  • every version up to 3.6.4-1: fixed in 3.6.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

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 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.2% probability of exploitation in the next 30 days (12th percentile of EPSS-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?
A fix for CVE-2026-75803 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75803 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs