CVE-2026-121481

CRITICALPre-NVD 5.99.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9; sources differ by 3.9.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-128602 (ENISA EUVD) · GHSA-83xj-7xh4-4p7x (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer.

Impact summary: No path by which an attacker can trigger this has been identified. An application that passes an input length near INT_MAX to EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting its own memory, but it must itself supply such a length.

CWE: CWE-190: Integer Overflow or Wraparound

Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied length into an output buffer that the caller allocates. The caller is expected to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the arithmetic that computes the encoded length overflows a signed integer, so the function writes more data than the documented output size. The result is a heap buffer overflow in the calling process.

Reaching this requires an application to pass an input length near INT_MAX to EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode buffers of that size, and the command line tools cannot practically be made to do so: the limits on reading a proxy password from a file and on bignum sizes prevent it. An application that accepts an attacker-controlled length and forwards it to EVP_EncodeBlock() without its own bound check is exposed.

The severity is Low because no attacker-controlled path to the overflow is known. The caller must already hold a buffer of about two gigabytes before the defect can be reached.

FIPS impact: no The affected code is outside the FIPS module boundary.

CVSS v3
5.9
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
40th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 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.

The score's inputs: 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

November 18, 2026

Last Modified

November 20, 2026

Advisory Details (2)

Auto-updated Nov 20, 2026
Patch available. Sources: github_pr.
Web page

OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-121481, CVSS 9.8) | Hacker News

https://news.ycombinator.com/item?id=50569226
GitHub pull request

[NSF] [CVE-2026-121481] Buffer overflow in EVP_EncodeBlock()

Upstream fix in progress (PR #33652 · openssl/openssl, state=open)

https://github.com/openssl/openssl/pull/33652

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenssl3-main-3.5.9-1.3.hum12026-11-12redhat
redhatopenssl-main-3.5.9-0.4.hum12026-11-11redhat
redhatruby3-3-main-3.3.13-23.8.hum12026-10-24redhat
redhatruby3-4-main-3.4.12-33.1.hum12026-10-23redhat
redhatpython-cryptography-main-50.0.0-1.1.hum12026-10-12redhat
redhatrust-bootupd-main-0.3.2-1.1.hum12026-10-12redhat
redhatchunkah-main-0.7.1-1.hum12026-10-08redhat

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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.

  1. 2026-11-21 21:44 UTCEchelonGraph re-scored
  2. 2026-11-21 21:44 UTCVendor advisory
  3. 2026-11-21 21:44 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-20 20:28 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-20 19:52 UTCEchelonGraph re-scored
  7. 2026-11-20 19:52 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-20 19:51 UTCMITRE cvelistV5CVSS v3 → 5.9 · severity → MEDIUM
  9. 2026-11-20 19:28 UTCEchelonGraph re-scored
  10. 2026-11-20 19:28 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-20 19:27 UTCNVD updateCVSS → 8.4 · severity → HIGH
  12. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-11-20 10:21 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-20 05:28 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-20 04:38 UTCEchelonGraph re-scored
  16. 2026-11-20 04:38 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-19 22:29 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x
  18. 2026-11-19 21:28 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  19. 2026-11-19 21:28 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x
  20. 2026-11-19 21:27 UTCMITRE cvelistV5CVSS → 9.8 · severity → CRITICAL
  21. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-11-18 13:03 UTCENISA EUVD ID recordedEUVD-2026-128602 · Source: ENISA EUVD
  23. 2026-11-18 12:49 UTCGHSA enrichmentGHSA-83xj-7xh4-4p7x
  24. 2026-11-18 11:48 UTCEchelonGraph re-scored
  25. 2026-11-18 11:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-121481?
CVE-2026-121481 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer. Impact summary: No path by which an attacker can trigger this has been identified. An application that…
When was the CVE record for CVE-2026-121481 published?
The CVE record for CVE-2026-121481 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-121481 actively exploited?
CVE-2026-121481 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-121481?
CVE-2026-121481 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises CISA-ADP (Vulnrichment) CVSS v3.1 + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2026-121481?
A fix for CVE-2026-121481 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-121481 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-121481

Explore →

Is Your Infrastructure Affected by CVE-2026-121481?

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