CVE-2025-11187: Stack Buffer Overflow in OpenSSL PKCS#12 PBMAC1 Verification
- Vendor
- OpenSSL Software Foundation
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.
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.
Exploits
1 exploit validated by Mallory's analysis.
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.
References
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.
Recent activity
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.