Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisoryproof-of-concept-release

OpenSSL January Security Update Fixes CMS and PKCS#12 Stack Overflows With RCE Risk

Vulnerability Disclosure · 5 sources · Updated 5mo ago · First seen Jan 28, 2026

OpenSSL January Security Update Fixes CMS and PKCS#12 Stack Overflows With RCE Risk

OpenSSL released a security update on January 27, 2026, addressing 12 vulnerabilities across supported branches, including one High-severity issue with potential remote code execution (RCE), one Moderate, and multiple Low-severity flaws. The most serious vulnerability, CVE-2025-15467 (High), is a pre-authentication stack buffer overflow in CMS AuthEnvelopedData parsing when using AEAD ciphers (e.g., AES-GCM); a crafted CMS message with an oversized IV in ASN.1 parameters can trigger a crash and may enable code execution in applications that parse untrusted CMS/PKCS#7 content (notably S/MIME workflows). Both sources emphasize that while DoS is the most likely outcome in many environments, the presence of a stack write primitive makes the issue operationally significant where untrusted CMS is processed.

A second notable issue, CVE-2025-11187 (Moderate), involves a stack overflow during PKCS#12 MAC verification (PBMAC1/PBKDF2-related validation), where attacker-controlled parameters (e.g., key length) can lead to crashes and potentially more severe impact when processing untrusted PKCS#12 files (e.g., certificate import/export, PKI/CA tooling). Affected versions called out include OpenSSL 3.x (with additional low-severity issues spanning older branches such as 1.0.2 and 1.1.1), and patched releases include 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19 (with corresponding fixes for older maintained lines). Datadog notes OpenSSL 3.x FIPS modules are not affected by the highlighted CMS and PKCS#12 overflow issues, and both sources point to higher risk in services that ingest these formats from external or user-supplied inputs (e.g., S/MIME gateways, certificate management services).

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Jan 27, 2026 – Jan 29, 2026
  1. Jan 29, 202610mo ago

    Aisle discovers 12 OpenSSL vulnerabilities

    Cybersecurity firm Aisle identified 12 previously undetected vulnerabilities in OpenSSL, including CVE-2025-15467 and CVE-2025-11187. One source says some of the flaws may have existed in the codebase since 1998.

  2. Jan 27, 202610mo ago

    OpenSSL releases patched versions for affected branches

    OpenSSL released fixes for the 12 vulnerabilities and recommended upgrading to patched versions including 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19, and premium 1.1.1ze and 1.0.2zn. The project also advised limiting exposure to untrusted CMS and PKCS#12 inputs because exploitability depends on whether applications parse such data.

  3. Jan 27, 202610mo ago

    OpenSSL publishes January 2026 security advisory for 12 flaws

    On January 27, 2026, the OpenSSL project disclosed details for 12 vulnerabilities affecting versions 1.0.2, 1.1.1, and multiple 3.x releases. The advisory highlighted high-severity CVE-2025-15467 in CMS AuthEnvelopedData parsing, moderate-severity CVE-2025-11187 in PKCS#12 PBMAC1 validation, and 10 low-severity issues.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.