CVE-2026-9076

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — Patch released this week

Also known asEUVD-2026-35475 (ENISA EUVD) · GHSA-q98x-73c3-57gj (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • 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 CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key().

Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.

The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on the wrapped key length from the message. There is a minimum length check based on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can happen.

Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is required: the over-read happens during the unwrap attempt before any authentication succeeds.

The over-read is limited to a few bytes and is not written to output, so there is no information disclosure. Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal allocator.

The FIPS modules are not affected by this issue.

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

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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 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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available.

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
oraclepatch2026-11-17oracle
ubuntuopenssl (3.0.13-0ubuntu3.11) @ noble2026-11-17ubuntu
ubuntuopenssl (1.0.2g-1ubuntu4.20+esm16) @ xenial2026-11-17ubuntu
oraclepatch2026-10-20oracle
oraclepatch2026-10-20oracle
redhatcert-manager/cert-manager-operator-bundle:17919662592026-10-14redhat
redhatcert-manager/cert-manager-operator-bundle:17919704842026-10-14redhat
redhatcert-manager/cert-manager-operator-rhel9:17917882872026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17914597112026-10-13redhat
redhatcert-manager/cert-manager-operator-rhel9:17890290762026-10-13redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17914597592026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17913710692026-10-13redhat
redhatcert-manager/cert-manager-trust-manager-rhel9:17905985932026-09-28redhat
redhatrust-bootupd-main-0.3.2-1.hum12026-09-15redhat
redhatruby4-0-main-4.0.6-37.3.hum12026-09-02redhat
redhatruby3-3-main-3.3.10-23.6.hum12026-09-02redhat
redhatruby3-4-main-3.4.10-31.7.hum12026-09-02redhat
redhatopenssl-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatpython-cryptography-main-50.0.0-1.hum12026-08-17redhat
redhatchunkah-main-0.6.0-3.hum12026-07-21redhat
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

These rows come from Oracle, Ubuntu and Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.3.7-r1: fixed in 3.3.7-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1k-1 ... 1.1.1w-0~deb11u1 (23 versions)
  • every version up to 1.1.1w-0+deb11u8: fixed in 1.1.1w-0+deb11u8
—
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

(9)

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 438 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 338 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-9076?
CVE-2026-9076 is a high-severity vulnerability; its CVE record was published on June 9, 2026. Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key(). Impact summary: A heap buffer over-read may trigger a crash which leads to Denial…
When was CVE-2026-9076 made public?
CVE-2026-9076 was made public on June 9, 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 June 9, 2026. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-9076 actively exploited?
CVE-2026-9076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9076?
CVE-2026-9076 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-9076?
A fix for CVE-2026-9076 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9076 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's 2 advisories for CVE-2026-9076 are also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9076

Explore →

Is Your Infrastructure Affected by CVE-2026-9076?

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