Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2025-11187: Stack Buffer Overflow in OpenSSL PKCS#12 PBMAC1 Verification

Published Jan 27, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS6.1Medium · v3.1
EPSS5.2%93rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-11187CWE-121

CVE-2025-11187 is a parameter-validation vulnerability in OpenSSL PKCS#12 MAC verification affecting versions 3.4.0–3.4.3, 3.5.0–3.5.4, and 3.6.0. When verifying a PKCS#12 file using PBMAC1, OpenSSL uses embedded PBKDF2 salt and keylength parameters without adequate validation. A keylength exceeding the fixed 64-byte stack buffer allocated for the derived key triggers a stack-based buffer overflow whose length is attacker-controlled. A salt parameter with a type other than OCTET STRING can instead trigger an invalid or NULL pointer dereference. Processing a maliciously crafted file can cause denial of service and potentially code execution. OpenSSL 3.3, 3.0, 1.1.1, and 1.0.2 lack PKCS#12 PBMAC1 support and are unaffected. The FIPS modules are unaffected because PKCS#12 processing occurs outside their boundary.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Applications verifying attacker-controlled PKCS#12 files can crash through stack corruption or invalid/NULL pointer dereferences, causing denial of service. The stack overflow may additionally permit arbitrary code execution in the affected application's security context, depending on platform mitigations. The issue is assessed as Moderate because applications rarely accept untrusted PKCS#12 files.

Mitigation

If you can’t patch tonight, do this now.

Avoid processing untrusted PKCS#12 files and restrict import and verification workflows to trusted sources until patched. Where external files must be accepted, isolate parsing in a sandbox and execute it with minimal privileges to limit the consequences of exploitation.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to version 3.4.4, 3.5.5, or 3.6.1, or a later supported release in the applicable branch. For distribution-provided or embedded OpenSSL, install the vendor's security update containing the fix rather than relying solely on the upstream version number.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2025-11187This repository is a real proof-of-concept for CVE-2025-11187, a stack buffer overflow in OpenSSL 3.x PKCS#12 PBMAC1/PBKDF2 handling. The bug is described as occurring when an attacker controls the PBKDF2 keylength embedded in PBMAC1 parameters; OpenSSL later uses that oversized key length in MAC generation/verification, causing a write past a fixed-size stack buffer in libcrypto (notably pkcs12_gen_mac() / PBMAC1_PBKDF2_HMAC in crypto/pkcs12/p12_mutl.c, with the overflow surfacing in PBKDF2 code paths). Repository structure is small and focused: three C PoCs under src/, build instructions in a Makefile, reproduction notes in docs/, sanitizer/crash logs in logs/, and a patch diff in patch/ showing the intended remediation. The default build target is src/poc_public.c, which is the main public PoC. It constructs a minimal PKCS#12 object in memory, calls PKCS12_set_pbmac1_pbkdf2() to initialize PBMAC1, then manually unpacks and rewrites the embedded PBKDF2 parameters so keylength becomes attacker-controlled. It finally invokes PKCS12_verify_mac(), which triggers the vulnerable path. The CLI accepts <keylength> [iter] [digest], making it easy to test values like 4096, 1000, sha256. The internal PoCs are more direct. src/poc_internal.c uses internal OpenSSL structures/headers to build a PKCS#12 object, replace the MAC algorithm parameters with a crafted PBMAC1PARAM containing a large key length, and then call PKCS12_verify_mac(). src/poc_internal_cli.c similarly exposes keylength, iteration count, and digest via command line, but calls PKCS12_gen_mac() instead of verify, demonstrating the same unsafe handling from a slightly different path. There are no network capabilities, C2, remote callbacks, or external service endpoints. The attack vector is local/file-based: a malicious PKCS#12 structure is created in memory to emulate parsing or verifying a hostile PKCS#12 file. The included logs show UBSan/ASan traces confirming undefined behavior and a stack-buffer-overflow, with the key buffer in pkcs12_gen_mac() being overrun. The patch diff adds a simple bounds check rejecting key lengths <= 0 or greater than EVP_MAX_MD_SIZE before invoking PKCS5_PBKDF2_HMAC, which aligns with the demonstrated root cause. Overall, this is a focused denial-of-service memory-corruption PoC repository for OpenSSL PKCS#12 PBMAC1 handling, intended for vulnerability reproduction and validation rather than post-exploitation.metadust · Disclosed Mar 15, 2026 · c · makefile · local · filePoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

Frequently asked questions

Is CVE-2025-11187 exploited in the wild?
As of Nov 10, 2026, Mallory has no reports of CVE-2025-11187 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-11187?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-11187, the earliest disclosed Mar 15, 2026.
Is there a patch for CVE-2025-11187?
Upgrade OpenSSL to version 3.4.4, 3.5.5, or 3.6.1, or a later supported release in the applicable branch. For distribution-provided or embedded OpenSSL, install the vendor's security update containing the fix rather than relying solely on the upstream version number.
What products are affected by CVE-2025-11187?
OpenSSL Software Foundation Openssl.
How severe is CVE-2025-11187?
CVE-2025-11187 has a CVSS v3.1 score of 6.1 (Medium) and an EPSS score of 5.2% (93rd percentile) as of Nov 10, 2026.
Activity feed

Recent activity

50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity21Community discussion across Reddit, Mastodon, and other social sources.