# CVE-2026-121481 — OpenSSL

> As of 2026-11-20, CVE-2026-121481 is a MEDIUM-severity vulnerability in OpenSSL, CVSS v3.1 5.9, EPSS 0.3% (24.1th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-121481, most recently “OpenSSL Integer Overflow Leading to Heap Buffer Overflow in EVP_EncodeBlock() Base64 Encoding (CVE-2026-121481)”.

**Last updated:** 2026-11-20

## What is CVE-2026-121481?

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.

The record classifies CVE-2026-121481 under weakness class [CWE-190](https://intel.threadlinqs.com/cwe/CWE-190). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.9 — MEDIUM (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 24.1% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 5.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-18

## Is CVE-2026-121481 being exploited?

Weaponised exploit code for CVE-2026-121481 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 49 in the Threadlinqs vulnerability feed.

- [Quaerendir/openssl-cve-2026-121481-audit](https://github.com/Quaerendir/openssl-cve-2026-121481-audit) (github)

## Affected products and versions

- [OpenSSL](https://intel.threadlinqs.com/vendors/openssl): OpenSSL

## How to fix CVE-2026-121481

The record marks a vendor fix as available for CVE-2026-121481. Patch reference: [https://github.com/openssl/openssl/pull/33652](https://github.com/openssl/openssl/pull/33652). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-121481

1 tracked threat in the Threadlinqs corpus references CVE-2026-121481, either in the campaign’s CVE list or as an indicator on the campaign record.

- [OpenSSL Integer Overflow Leading to Heap Buffer Overflow in EVP_EncodeBlock() Base64 Encoding (CVE-2026-121481)](https://intel.threadlinqs.com/threat/TL-2026-6579) — CRITICAL · 2026-11-20

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/openssl/openssl/pull/33652)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-121481
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents (Purple and Gold in full, 2 calls a day on a free account): https://intel.threadlinqs.com/mcp
