OpenSSL is widely used across industries; vulnerability in 3.x affects many products and could lead to remote code execution.
CVE-2025-15467
OpenSSL 3.x CMS AuthEnvelopedData overflow risks DoS or RCE.
Is CVE-2025-15467 being exploited?
Not confirmed. CVE-2025-15467 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 48% probability of exploitation in the next 30 days.
How severe is CVE-2025-15467?
CVE-2025-15467 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-15467?
Yes. A fix has been recorded for CVE-2025-15467. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-15467 affect?
CVE-2025-15467 affects OpenSSL 3.x (CMS/AuthEnvelopedData with AES-GCM). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-15467?
Upgrade to patched OpenSSL 3.x release; apply advisory
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted CMS message with oversized AES-GCM IV triggers stack overflow before auth, enabling DoS and possible RCE.
Immediate action required
- affected>= 3.6.0 and < 3.6.1
- affected>= 3.5.0 and < 3.5.5
- affected>= 3.4.0 and < 3.4.4
- affected>= 3.3.0 and < 3.3.6
- affected>= 3.0.0 and < 3.0.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.