CVE-2025-69421: Denial of Service in OpenSSL PKCS#12 Processing
- Vendor
- OpenSSL Software Foundation
CVE-2025-69421 is a NULL pointer dereference vulnerability in OpenSSL's PKCS12_item_decrypt_d2i_ex() function. The function dereferences its oct parameter without checking whether it is NULL. Processing a malformed PKCS#12 file through PKCS12_unpack_p7encdata() can supply a NULL oct parameter, crashing the application. Vulnerable release branches include OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, and 1.0.2 before applicable fixes. The impact is limited to denial of service; the vulnerability cannot be escalated to code execution or memory disclosure. The OpenSSL FIPS modules in branches 3.6, 3.5, 3.4, 3.3, and 3.0 are unaffected because PKCS#12 processing is outside their module boundaries; applications using those modules may still expose the vulnerable PKCS#12 implementation.
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.
A malformed attacker-supplied PKCS#12 file can crash the application processing it, interrupting service availability. There is no code-execution or memory-disclosure impact. The upstream assessment is Low severity because exploitation requires an application to process an attacker-supplied file; several downstream assessments assign CVSS 7.5 for network-exposed processing scenarios.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid processing untrusted PKCS#12 files and restrict PKCS#12 upload or import functionality to trusted sources and authorized users. Where feasible, disable externally accessible PKCS#12 processing. Input filtering can reduce exposure but should not be treated as a substitute for the NULL-pointer validation fix.
Remediation
Patch, then assume compromise.
Install the applicable vendor-fixed OpenSSL release or distribution security update. Fixed OpenSSL releases identified for the maintained 3.x branches are 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19. For OpenSSL 1.1.1 and 1.0.2, obtain an applicable supported-vendor fix or migrate to a supported, patched branch; exact fixed versions for these branches are not specified. Update products that bundle OpenSSL through their vendor updates rather than assuming a system-library update covers embedded copies. Distribution backports may retain earlier upstream version numbers.
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-69421 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2025-69421 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-69421?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-69421, the earliest disclosed Jul 22, 2026.
- Is there a patch for CVE-2025-69421?
- Install the applicable vendor-fixed OpenSSL release or distribution security update. Fixed OpenSSL releases identified for the maintained 3.x branches are 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19.
- What products are affected by CVE-2025-69421?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2025-69421?
- CVE-2025-69421 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.94% (62nd percentile) as of Nov 7, 2026.
Recent activity
54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.