CVE-2025-69418

MEDIUMNVD 4.04.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.0 from GitHub Security Advisory published 2026-01-27. NVD baseline CVSS 4.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this week
4.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: When using the low-level OCB API directly with AES-NI orother hardware-accelerated code paths, inputs whose length is not a multipleof 16 bytes can leave the final partial block unencrypted and unauthenticated.Impact summary: The trailing 1-15 bytes of a message may be exposed incleartext on encryption and are not covered by the authentication tag,allowing an attacker to read or tamper with those bytes without detection.The low-level OCB encrypt and decrypt routines in the hardware-acceleratedstream path process full 16-byte blocks but do not advance the input/outputpointers. The subsequent tail-handling code then operates on the originalbase pointers, effectively reprocessing the beginning of the buffer whileleaving the actual trailing bytes unprocessed. The authentication checksumalso excludes the true tail bytes.However, typical OpenSSL consumers using EVP are not affected because thehigher-level EVP and provider OCB implementations split inputs so that fullblocks and trailing partial blocks are processed in separate calls, avoidingthe problematic code path. Additionally, TLS does not use OCB ciphersuites.The vulnerability only affects applications that call the low-levelCRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly withnon-block-aligned lengths in a single call on hardware-accelerated builds.For these reasons the issue was assessed as Low severity.The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affectedby this issue, as OCB mode is not a FIPS-approved algorithm.OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.OpenSSL 1.0.2 is not affected by this issue.

CVSS v3
4.0
EG Score
4.0MEDIUMmedium confidence
EG Risk
18
EG Risk 18/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 (value × EchelonGraph’s weight)
Severity40% × 45%
The EG Score, 4.0 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 27, 2026

Last Modified

October 15, 2026

Advisory Details (7)

Auto-updated Aug 9, 2026
Patch available. Sources: github_commit.
Web page

SSA-265688

https://cert-portal.siemens.com/productcert/html/ssa-265688.html
Web page
https://openssl-library.org/news/secadv/20260127.txt
GitHub commit

commit ed40856d7d4b (openssl/openssl)

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

https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
GitHub commit

commit a7589230356d (openssl/openssl)

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

https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
GitHub commit

commit 52d23c86a54a (openssl/openssl)

Fix landed in openssl/openssl commit 52d23c86a54a — awaiting tagged release

https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
GitHub commit

commit 4016975d4469 (openssl/openssl)

Fix landed in openssl/openssl commit 4016975d4469 — awaiting tagged release

https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
GitHub commit

commit 372fc5c77529 (openssl/openssl)

Fix landed in openssl/openssl commit 372fc5c77529 — awaiting tagged release

https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc

Vendor Advisories for CVE-2025-69418(14)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl (1.1.1f-1ubuntu2.24+esm2) @ focal2026-10-15ubuntu
ubuntuopenssl-provider-legacy (3.5.3-1ubuntu3) @ questing2026-10-15ubuntu
redhatcert-manager/cert-manager-istio-csr-rhel9:17914597592026-10-13redhat
redhatcert-manager/cert-manager-operator-rhel9:17890290762026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17914597112026-10-13redhat
redhatopenssl-1:3.2.2-16.el10_0.72026-09-24redhat
redhatopenssl-main-3.5.6-0.1.hum12026-04-09redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17708363492026-02-24redhat
redhatrhui5/installer-rhel9:17706469252026-02-11redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17707404052026-02-10redhat
redhatdiscovery/discovery-ui-rhel9:17691117742026-02-02redhat
redhatopenssl-1:3.5.1-7.el9_72026-01-28redhat
redhatopenssl-1:3.5.1-7.el10_12026-01-28redhat

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

(10 across 10 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.1 up to 3.0.19-r0: fixed in 3.0.19-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.1 up to 3.3.6-r0: fixed in 3.3.6-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.1 up to 3.3.6-r0: fixed in 3.3.6-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.1 up to 3.5.5-r0: fixed in 3.5.5-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.1 up to 3.5.5-r0: fixed in 3.5.5-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.1 up to 3.5.5-r0: fixed in 3.5.5-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1k-1 ... 1.1.1w-0~deb11u1 (20 versions)
  • every version up to 1.1.1w-0+deb11u5: fixed in 1.1.1w-0+deb11u5
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.0.10-1 ... 3.0.9-1 (18 versions)
  • every version up to 3.0.18-1~deb12u2: fixed in 3.0.18-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1, 3.5.1-1+deb13u1, 3.5.2-1, 3.5.3-1, 3.5.4-1~deb13u1
  • every version up to 3.5.4-1~deb13u2: fixed in 3.5.4-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.5.5-1~deb13u2 (8 versions)
  • every version up to 3.5.5-1: fixed in 3.5.5-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 14× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2025-69418?
CVE-2025-69418 is a medium-severity vulnerability; its CVE record was published on January 27, 2026. Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may…
When was CVE-2025-69418 made public?
CVE-2025-69418 was made public on January 27, 2026: that is the date its CVE record's CNA, OpenSSL Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on January 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2025-69418 actively exploited?
CVE-2025-69418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-69418?
CVE-2025-69418 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2025-69418?
A fix for CVE-2025-69418 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-69418 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-2025-69418

Explore →

Is Your Infrastructure Affected by CVE-2025-69418?

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

Book a Demo →Browse All CVEs