Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-15467: Stack Buffer Overflow in OpenSSL CMS AEAD Parameter Parsing

Published Jan 27, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days13 mentions · peak 4 in a dayToday
CVSS9.8Critical · v3.1
EPSS74.8%100th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
Oracle CorporationOpenSSL Software Foundation
IdentifiersCVE-2025-15467CWE-121

CVE-2025-15467 is a stack-based buffer overflow in OpenSSL's parsing of CMS AuthEnvelopedData and EnvelopedData structures using AEAD ciphers such as AES-GCM. An initialization vector encoded in ASN.1 parameters is copied into a fixed-size stack buffer without checking that its length fits the destination. A crafted message containing an oversized initialization vector triggers an out-of-bounds write before authentication or tag verification. Applications processing untrusted CMS or PKCS#7 content, including applicable S/MIME messages, can suffer denial of service or potentially remote code execution. Affected release families include OpenSSL 3.0, 3.3, 3.4, 3.5, and 3.6; OpenSSL 1.1.1 and 1.0.2 are unaffected. The corresponding FIPS modules are unaffected because CMS processing lies outside their boundaries, but applications using those modules can still expose the vulnerable CMS 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.

Exploitation can corrupt stack memory and crash the processing application or service, causing denial of service. Potential remote code execution could compromise confidentiality, integrity, and availability within the affected process's security context. Code-execution feasibility depends on platform and toolchain protections and is not established for every affected deployment. Neither valid cryptographic key material nor successful message authentication is necessary to trigger the overflow.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid processing untrusted CMS or PKCS#7 AuthEnvelopedData and EnvelopedData messages using AEAD ciphers. Disable or restrict affected message-processing workflows where operationally feasible, reject files from untrusted or unvalidated sources, and limit network access to services accepting CMS or S/MIME input. Apply segmentation and access controls to reduce exposure. FIPS-module use alone does not mitigate the vulnerable CMS parsing path.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to 3.6.1, 3.5.5, 3.4.4, 3.3.6, or 3.0.19, as appropriate for the deployed branch, or a later supported patched release. For distribution packages and products bundling OpenSSL, install the vendor's applicable security update rather than relying solely on upstream version comparisons. Refresh affected container images and restart applications using the updated libraries. Product-specific fixes include Siemens Desigo CC V8.0 QU2.0021 and V9.0 QU1 or later.

Public exploits

Exploits

5 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2025-15467Repository provides a network-triggerable DoS proof-of-concept for CVE-2025-15467 (OpenSSL CMS AuthEnvelopedData parsing stack buffer overflow in evp_cipher_get_asn1_aead_params()). Structure/purpose: - dos.py: Standalone Python exploit that constructs a DER-encoded CMS ContentInfo/AuthEnvelopedData object. It embeds AES-256-GCM GCMParameters with an oversized nonce/IV (default 512 bytes) intended to overflow a 16-byte stack buffer during OpenSSL’s AEAD parameter parsing. The script delivers the payload via raw TCP HTTP POST (Content-Type: application/cms) to a configurable endpoint (default /cms), then checks liveness via GET /health to confirm a crash. - vulnerable_service/: A Dockerized intentionally vulnerable HTTP service to reproduce the issue. - cms_server.c: Minimal multithreaded HTTP server exposing GET /version, GET /health, and POST /cms. The /cms handler reads request body and calls d2i_CMS_bio() followed by CMS_decrypt(), which triggers the vulnerable code path when parsing AEAD parameters. - Dockerfile: Builds OpenSSL 3.0.14 from source and compiles cms_server with exploit-friendly flags (-fno-stack-protector, -z execstack, -no-pie). Exposes port 8080. - entrypoint.sh: Attempts to disable ASLR via /proc/sys/kernel/randomize_va_space (requires --privileged) and runs the server in an auto-restart loop to facilitate repeated crash testing. Exploit capability: - Primary: Remote denial-of-service (process crash) against services that parse CMS/PKCS#7 AuthEnvelopedData using vulnerable OpenSSL versions. - The repo mentions potential RCE in theory, and the container reduces mitigations, but the provided exploit code itself is DoS-oriented and does not implement code execution primitives.balgan · Disclosed Jan 28, 2026 · python · c · networkOperationalCVE-2025-15467Repository purpose: a proof-of-concept/operational exploit for a claimed OpenSSL CMS AuthEnvelopedData AES-GCM IV parsing stack buffer overflow (CVE-2025-15467), resulting in code execution when a victim application decrypts/parses a malicious CMS/PKCS#7 (DER) object. Structure (5 files): - exploit.py (~22 KB): primary exploit generator. It takes a valid CMS file as a template and patches the AES-GCM IV (nonce) OCTET STRING to an oversized value that overflows a fixed 16-byte stack buffer in OpenSSL’s evp_cipher_get_asn1_aead_params(). The payload layout is padding to saved RIP (RIP_OFFSET=56), followed by a ROP chain that calls mprotect() on the stack page (RWX) and then transfers execution to stack-resident shellcode via a jmp/call rsp gadget. Embedded x86_64 shellcode performs execve("/bin/sh", NULL, NULL). - Supports two modes: - Auto mode (--auto): intended to discover runtime addresses (libc/libcrypto/stack) using GDB and optionally pwntools for gadget discovery (the provided content shows a truncated implementation, but the intent is clear from function names and README usage). - Manual mode: user supplies libcrypto base, libc base, and a stack address (RSP) to build absolute addresses for the ROP chain. - setup.sh (~2.2 KB): builds and installs OpenSSL 3.4.0 into /opt/openssl-vuln with exploit-friendly flags (no stack protector, execstack, no PIE) and generates dummy.key/dummy.crt and a valid.cms template in /tmp. - README.md / TECHNICAL.md: documentation and technical deep-dive, including the vulnerable code snippet, call chain (CMS_decrypt → … → evp_cipher_get_asn1_aead_params), stack layout, and example gadget offsets for specific library versions. Exploit capabilities: - Generates a malicious CMS DER file by modifying the AES-GCM IV field to exceed EVP_MAX_IV_LENGTH (16), triggering a stack overflow during CMS decryption/parsing. - Achieves instruction pointer control and executes a ROP chain to bypass NX by calling mprotect() on the stack. - Executes embedded x86_64 shellcode to spawn /bin/sh, yielding a shell in the context of the vulnerable process. Attack surface/targets: - Any application that processes untrusted CMS/S/MIME/PKCS#7 AuthEnvelopedData using vulnerable OpenSSL versions (claimed 3.0–3.6 pre-fix), especially when decrypting CMS with AES-GCM parameters. Notable observables: - No hardcoded C2 network infrastructure; the exploit is file-based (malicious CMS) and local execution is demonstrated via invoking the openssl cms -decrypt command. - Fingerprintable paths and URLs include /opt/openssl-vuln, /proc/sys/kernel/randomize_va_space, /tmp/{dummy.key,dummy.crt,valid.cms}, and https://www.openssl.org/source/openssl-3.4.0.tar.gz.guiimoraes · Disclosed Jan 30, 2026 · python · bash · network (remote via parsing malicious CMS/S/MIME/PKCS#7 content by a vulnerable application)Operationalcve-2025-15467This repository is a small Python-based exploit lab for CVE-2025-15467. It contains two substantive files: cms_server.py, a Flask application simulating a vulnerable CMS/S/MIME decryption service, and exploit.py, the attacker script. README.md is minimal and only labels the repository. The vulnerable service listens on port 8080 and exposes a simple web UI plus four API routes: /cert, /sample, /version, and /decrypt. Internally it shells out to /opt/openssl-vuln/bin/openssl with LD_LIBRARY_PATH set to /opt/openssl-vuln/lib64, using cms -decrypt against uploaded DER CMS content. The service returns plaintext on success, structured error output on parse/decrypt failure, and explicit crash metadata when the OpenSSL subprocess dies from a signal such as SIGSEGV. This makes it suitable as a lab target and also provides a direct crash oracle. The exploit script is a standalone Python exploit, not part of a larger framework. Based on the visible code and embedded documentation, it implements a network attack against the HTTP decryption endpoint. The exploit chain is: fetch a valid CMS object from the target (/sample), modify the CMS/AuthEnvelopedData structure so the AEAD IV becomes oversized, and send the malicious CMS back to /decrypt. The script states the bug is a stack buffer overflow in evp_cipher_get_asn1_aead_params() where attacker-controlled IV data is copied into a fixed 16-byte stack buffer. It uses a hardcoded RIP offset of 56 bytes and a hardcoded jmp rsp gadget address (0x7ffff7ae841d) for a Linux/amd64 Ubuntu 22.04-style environment with ASLR disabled. Exploit capabilities include: (1) crash mode for denial of service without needing code-reuse addresses, (2) RCE proof mode that executes amd64 shellcode to create /tmp/pwn and write marker content, and (3) reverse shell mode that generates callback shellcode to an attacker-supplied IP and port. The script can use pwntools for shellcode generation if installed, but also includes a manual fallback shellcode path for the file-creation payload. The exploit is therefore more than a PoC: it contains working payload logic, but it is still environment-specific due to hardcoded gadget assumptions and ASLR requirements. Overall, the repository’s purpose is to demonstrate and test exploitation of a vulnerable OpenSSL CMS parsing path in a controlled lab setting. The server file provides the target surface and the exploit file automates both crash verification and code-execution attempts against that surface.materaj2 · Disclosed Mar 14, 2026 · python · markdown · networkOperationalcve-2025-15467-crashThe repository contains a single GitHub Actions workflow, .github/workflows/blank.yml, which serves as the entire exploit. It is not a traditional source repository but an automation script that builds and exercises a proof-of-concept for CVE-2025-15467 against OpenSSL 3.4.0. Structure and purpose: the workflow has one job that (1) checks out the repository, (2) installs build dependencies, (3) downloads OpenSSL 3.4.0 from openssl.org, (4) compiles it locally with reduced exploit mitigations (-fno-stack-protector, disabled FORTIFY, -O0, execstack), (5) generates a self-signed certificate and a valid CMS encrypted template, (6) writes an inline Python script create_malicious.py that edits the DER-encoded CMS object to replace the expected GCM IV OCTET STRING with an oversized 168-byte field, and (7) invokes openssl cms -decrypt on the crafted exploit.cms to trigger a crash. Finally, it uploads the generated artifacts and logs. Main exploit capability: denial-of-service via process crash. The exploit does not provide code execution, a shell, or post-exploitation features. Its goal is to reliably trigger a stack buffer overflow condition in CMS decryption handling and demonstrate the vulnerability through SIGSEGV or stack-smashing termination. Attack surface: primarily local/file-based. The malformed input is a crafted CMS DER file consumed by the vulnerable OpenSSL binary. There is also a supply-chain style aspect because the exploit is packaged as CI automation that fetches and builds a specific vulnerable dependency version inside GitHub Actions. Notable implementation details: the Python payload logic searches the CMS template for the GCM IV OCTET STRING marker (preferring byte pattern 0x04 0x10), then replaces the original 16-byte IV encoding with a longer ASN.1 OCTET STRING header and 168 bytes of 'A'. The workflow uses LD_LIBRARY_PATH to ensure the locally built vulnerable libraries are loaded when generating and decrypting CMS content. Overall, this is an operational crash PoC embedded in CI rather than a standalone exploit program.WostGit · Disclosed Apr 7, 2026 · Framework: other · yaml · python · file · local · supply_chainOperationalCVE-2026-128027This standalone 22-file repository combines a stale-container-base demonstration with a working-style OpenSSL CMS memory-corruption trigger. Eight files contain executable or build logic: two Python programs, one C harness, two shell scripts, two Dockerfiles, and a Makefile. Compose configuration, documentation, metadata, and eight captured-evidence files complete the repository. poc/poc.py provides check, exploit, probe, and mitigation modes. poc/craft_cms.py independently generates the malformed DER input, while poc/cms_probe.c decodes it and calls CMS_decrypt without key material. poc/Dockerfile builds separate SHA-256-checked OpenSSL 3.3.5 and 3.3.6 source releases with AddressSanitizer. lab/ creates Alpine 3.21.5 and 3.21.6 containers that report their shipped package and library versions. run-lab.sh and Makefile orchestrate builds and comparisons. The supplied captures report a 4096-byte write beyond a 16-byte stack IV buffer on OpenSSL 3.3.5, followed by clean parameter rejection on 3.3.6. Importantly, the malformed CMS document is exercised locally in separately compiled probes, not delivered to the audit containers over HTTP. Neither FrankenPHP nor a remotely reachable CMS-processing application is installed by the target Dockerfile. Consequently, the lab illustrates stale dependency exposure and a local vulnerability differential, not end-to-end remote exploitation of FrankenPHP. Notable limitations: README.md and poc/poc.py are partially truncated, so the complete runner and exact registry URLs cannot be inspected. The documented /audit.json path differs from the actual /audit.cgi request, although the lab listener ignores paths and returns the same response. The mitigation mode treats any moving-tag digest different from the stale digest as patched, which is a heuristic rather than package-level verification. Compose publishes audit ports without an explicit localhost restriction. CITATION.cff also contains an inconsistent CVE-2026-128014 title, whereas the repository otherwise identifies CVE-2026-128027. No obvious malicious backdoor, exfiltration destination, or fake-exploit behavior appears in the visible code. Advisory identities, version claims, and committed evidence were not independently verified. Repository ref and archive size were not supplied; size_bytes is an unknown-value placeholder.googlesky · Disclosed Nov 14, 2026 · python · c · file · local · networkOperational
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
Oracle CorporationJD Edwards EnterpriseOne Toolsapplication
FAQ

Frequently asked questions

Is CVE-2025-15467 exploited in the wild?
Yes. As of Nov 14, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-15467?
Yes. Mallory tracks 5 public exploits or proofs of concept for CVE-2025-15467, the earliest disclosed Jan 28, 2026.
Is there a patch for CVE-2025-15467?
Upgrade OpenSSL to 3.6.1, 3.5.5, 3.4.4, 3.3.6, or 3.0.19, as appropriate for the deployed branch, or a later supported patched release. For distribution packages and products bundling OpenSSL, install the vendor's applicable security update rather than relying solely on upstream version comparisons.
What products are affected by CVE-2025-15467?
OpenSSL Software Foundation Openssl and Oracle Corporation JD Edwards EnterpriseOne Tools.
How severe is CVE-2025-15467?
CVE-2025-15467 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 74.8% (100th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

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

View more in app →
ghsa syntheticNews · Nov 13, 2026GHSA-vjcc-8rh5-xp2jA vulnerability in libcrypto3 cited as an example of a known flaw retained in stale FrankenPHP Docker images that could allow remote code execution. The content does not describe its underlying technical mechanism.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : openssl (EulerOS-SA-2026-4609) | Tenable®OpenSSL copies an attacker-controlled AEAD initialization vector into a fixed-size stack buffer without checking its length when parsing CMS messages. An oversized IV can cause denial of service or potentially remote code execution before authentication or tag verification, without valid key material. Affected applications include services processing untrusted CMS or PKCS#7 AEAD content, such as S/MIME messages using AES-GCM.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : openssl (EulerOS-SA-2026-4567) | Tenable®OpenSSL copies an attacker-controlled AEAD initialization vector into a fixed-size stack buffer without checking its length. Parsing crafted CMS or PKCS#7 encrypted content can cause denial of service or potentially remote code execution before authentication or tag verification; valid keys are not required. OpenSSL 1.1.1, 1.0.2 and the listed FIPS modules are unaffected. Updated EulerOS packages are available. The plugin reports exploit availability for the advisory collectively, but does not identify which individual CVEs have exploit code; per-CVE exploit availability therefore remains unspecified.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : edk2 (EulerOS-SA-2026-4584) | Tenable®OpenSSL copies an attacker-controlled initialization vector into a fixed-size stack buffer without checking its length when parsing CMS messages using AEAD ciphers. The overflow occurs before authentication and requires no valid key material. It can cause denial of service or potentially remote code execution. OpenSSL 3.0, 3.3, 3.4, 3.5 and 3.6 are identified as vulnerable; 1.0.2, 1.1.1 and the listed FIPS modules are not affected. The advisory includes this issue in EulerOS Virtualization's edk2 security update.Read more ↗
+51 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 malware2Malware 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 activity112Community discussion across Reddit, Mastodon, and other social sources.