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
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EPSS
24.3%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
No patch confirmed yet.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.2) @ resolute2026-07-16ubuntu
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.el10_22026-06-11redhat
redhatopenssl-1:3.5.5-4.el9_82026-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.

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 11× in last 7d / 102× 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 159 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 13:42 UTCVendor advisory
  9. 2026-07-16 13:42 UTCGHSA enrichment
  10. 2026-07-15 23:17 UTCVendor advisory
  11. 2026-07-15 23:17 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 10:09 UTCVendor advisory
  14. 2026-07-15 10:09 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 15:15 UTCVendor advisory
  17. 2026-07-14 15:15 UTCGHSA enrichment
  18. 2026-07-14 02:19 UTCVendor advisory
  19. 2026-07-14 02:19 UTCGHSA enrichment
  20. 2026-07-13 22:30 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 11:50 UTCVendor advisory
  23. 2026-07-12 11:50 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 22:45 UTCVendor advisory
Show 75 more
  1. 2026-07-11 22:45 UTCGHSA enrichment
  2. 2026-07-11 09:49 UTCVendor advisory
  3. 2026-07-11 09:49 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-10 20:53 UTCVendor advisory
  6. 2026-07-10 20:53 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 04:36 UTCVendor advisory
  9. 2026-07-09 04:36 UTCGHSA enrichment
  10. 2026-07-08 15:39 UTCVendor advisory
  11. 2026-07-08 15:39 UTCGHSA enrichment
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 01:30 UTCVendor advisory
  14. 2026-07-08 01:30 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 16:08 UTCVendor advisory
  19. 2026-07-05 16:08 UTCGHSA enrichment
  20. 2026-07-05 03:11 UTCVendor advisory
  21. 2026-07-05 03:11 UTCGHSA enrichment
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 14:13 UTCVendor advisory
  24. 2026-07-04 14:13 UTCGHSA enrichment
  25. 2026-07-04 06:31 UTCEPSS rescore
  26. 2026-07-03 22:12 UTCVendor advisory
  27. 2026-07-03 22:12 UTCGHSA enrichment
  28. 2026-07-03 09:17 UTCVendor advisory
  29. 2026-07-03 09:17 UTCGHSA enrichment
  30. 2026-07-02 20:20 UTCVendor advisory
  31. 2026-07-02 20:20 UTCGHSA enrichment
  32. 2026-07-02 07:21 UTCVendor advisory
  33. 2026-07-02 07:21 UTCGHSA enrichment
  34. 2026-07-01 18:18 UTCVendor advisory
  35. 2026-07-01 18:18 UTCGHSA enrichment
  36. 2026-07-01 15:07 UTCEPSS rescore
  37. 2026-07-01 05:20 UTCVendor advisory
  38. 2026-07-01 05:20 UTCGHSA enrichment
  39. 2026-06-30 23:22 UTCEPSS rescore
  40. 2026-06-30 15:30 UTCVendor advisory
  41. 2026-06-30 15:29 UTCGHSA enrichment
  42. 2026-06-29 23:36 UTCVendor advisory
  43. 2026-06-29 23:36 UTCGHSA enrichment
  44. 2026-06-29 10:41 UTCVendor advisory
  45. 2026-06-29 10:41 UTCGHSA enrichment
  46. 2026-06-28 21:34 UTCVendor advisory
  47. 2026-06-28 21:34 UTCGHSA enrichment
  48. 2026-06-28 14:07 UTCEPSS rescore
  49. 2026-06-28 08:37 UTCVendor advisory
  50. 2026-06-28 08:37 UTCGHSA enrichment
  51. 2026-06-28 04:56 UTCEPSS rescore
  52. 2026-06-28 04:56 UTCEPSS rescore
  53. 2026-06-27 19:42 UTCVendor advisory
  54. 2026-06-27 19:42 UTCGHSA enrichment
  55. 2026-06-27 06:44 UTCVendor advisory
  56. 2026-06-27 06:44 UTCGHSA enrichment
  57. 2026-06-27 03:08 UTCEPSS rescore
  58. 2026-06-26 17:48 UTCVendor advisory
  59. 2026-06-26 17:48 UTCGHSA enrichment
  60. 2026-06-26 04:53 UTCVendor advisory
  61. 2026-06-26 04:53 UTCGHSA enrichment
  62. 2026-06-25 15:56 UTCVendor advisory
  63. 2026-06-25 15:56 UTCGHSA enrichment
  64. 2026-06-25 13:49 UTCEPSS rescore
  65. 2026-06-25 02:52 UTCVendor advisory
  66. 2026-06-25 02:52 UTCGHSA enrichment
  67. 2026-06-24 14:05 UTCEPSS rescore
  68. 2026-06-24 13:55 UTCVendor advisory
  69. 2026-06-24 13:55 UTCGHSA enrichment
  70. 2026-06-24 00:49 UTCVendor advisory
  71. 2026-06-24 00:49 UTCGHSA enrichment
  72. 2026-06-23 21:33 UTCEPSS rescore
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-23 11:35 UTCVendor advisory
  75. 2026-06-23 11:35 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 in the National Vulnerability Database on June 9, 2026, with the most recent update on June 16, 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 24.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45445, 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-45445

Explore →

Is Your Infrastructure Affected by CVE-2026-45445?

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