Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-69421: Denial of Service in OpenSSL PKCS#12 Processing

Published Jan 27, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 6 in a dayToday
CVSS7.5High · v3.1
EPSS0.94%62nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-69421CWE-476 · NULL Pointer Dereference

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.

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.

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.

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-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.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : openssl (EulerOS-SA-2026-4609) | Tenable®OpenSSL fails to check whether the oct parameter is NULL before dereferencing it during PKCS#12 processing. An attacker-supplied malformed file can crash the processing application. The advisory explicitly limits the impact to denial of service, excluding code execution and memory disclosure.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : edk2 (EulerOS-SA-2026-4683) | Tenable®OpenSSL fails to validate a potentially NULL parameter during PKCS#12 processing, allowing a malformed file to crash the consuming application. The advisory explicitly limits the impact to denial of service, excluding code execution and memory disclosure. FIPS modules are unaffected. The plugin lists exploit availability and a proof-of-concept temporal rating, but does not explicitly attribute that availability to an individual CVE.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : shim (EulerOS-SA-2026-4619) | Tenable®A missing NULL check for the oct parameter in OpenSSL's PKCS12_item_decrypt_d2i_ex() function allows a malformed PKCS#12 file to crash an application processing it. The impact is limited to denial of service; the advisory explicitly excludes code execution and memory disclosure. OpenSSL rates the issue Low severity, while the Nessus listing assigns a High CVSS v3 base score of 7.5. Detection relies on the application's self-reported version rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : openssl (EulerOS-SA-2026-4567) | Tenable®A missing NULL check on the oct parameter in OpenSSL PKCS#12 processing allows a malformed file to crash an application. The advisory explicitly limits the impact to denial of service, excluding code execution and memory disclosure, and rates it Low severity. The listed FIPS modules are unaffected.Read more ↗
+25 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 activity15Community discussion across Reddit, Mastodon, and other social sources.