CVE-2025-15467
Stack buffer overflow in CMS (Auth)EnvelopedData parsing
Exploitation likely. EPSS gives it a 75% chance of exploitation in the next 30 days. Fixed versions are out.
No public exploit knownFix4 products4 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.118823
What to do
Find your product and version, then upgrade to the build on the right.
- OpenSSLAffected: ≥ 3.6.0, < 3.6.1Upgrade to: 3.6.1Affected: ≥ 3.5.0, < 3.5.5Upgrade to: 3.5.5Affected: ≥ 3.4.0, < 3.4.4Upgrade to: 3.4.4Affected: ≥ 3.3.0, < 3.3.6Upgrade to: 3.3.6 + 1 more branchStated by: CVE record
- ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
- ООО «РусБИТех-Астра» Astra Linux Special EditionAffected: 1.8Upgrade to: not statedStated by: BDU
- АО «СберТех» Platform V SberLinux OS ServerAffected: 9.2.0-fstecUpgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
Coverage timeline
2 publishersTechnical analysis published
Advisory coverage
Sourced from public security reporting — each date is when it was published, not when it happened.
What it is
From the CVE record
Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
75% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
47 events over 287 days, from the signal feeds we watch.
- Patch availableworkaround available, record updated
- Patch availableworkaround available, record updated
- EPSS band changemoderate → high
- EPSS band changemoderate → highepss band change
- Patch availableworkaround available, record updated
- Patch availableworkaround available, record updated
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored 8.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1190Exploit Public-Facing Applicationhigh confidence
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
References in the record
- openssl-library.org/news/secadv/20260127.txt
- github.com/openssl/openssl/commit/2c8f0e5fa9b6ee5508a0349e4572ddb74db5a703
- github.com/openssl/openssl/commit/d0071a0799f20cc8101730145349ed4487c268dc
And 52 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for OpenSSL, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI