CVE-2026-45445

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded.

Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message.

OpenSSL provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's streaming handler flushes the application-supplied IV into the OCB context before processing data; the one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero key-derived offset state left by cipher initialisation, regardless of the caller's IV.

If EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at that point and clears the running checksum that should have been accumulated over the plaintext. The resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same (key, IV) pair.

The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable.

The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module boundary.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.3-1ubuntu3.4) @ questing2026-09-14ubuntu
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17835391562026-07-15redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatopenssl-1:3.5.5-4.el9_82026-06-11redhat
redhatopenssl-1:3.5.5-4.el10_22026-06-11redhat

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.7-r0: fixed in 3.5.7-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.0.10-1 ... 3.0.9-1 (22 versions)
  • every version up to 3.0.20-1~deb12u2: fixed in 3.0.20-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.5.6-1~deb13u1 (11 versions)
  • every version up to 3.5.6-1~deb13u2: fixed in 3.5.6-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.6.2-1 (22 versions)
  • every version up to 3.6.3-1: fixed in 3.6.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 5× in last 7d / 24× 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 343 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45445?
CVE-2026-45445 is a high vulnerability published on June 9, 2026. Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV…
When was CVE-2026-45445 disclosed?
CVE-2026-45445 was first published on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45445 actively exploited?
CVE-2026-45445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45445?
CVE-2026-45445 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-45445?
A fix for CVE-2026-45445 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45445 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-45445

Explore →

Is Your Infrastructure Affected by CVE-2026-45445?

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