Finding and attribution
A crafted oversized AEAD IV in CMS AuthEnvelopedData or EnvelopedData can be copied into a fixed-size stack buffer before authentication. OpenSSL says impact may be denial of service or potentially remote code execution, depending on platform/toolchain mitigations.
Product: OpenSSL. AI system: AISLE autonomous analyzer (specific model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2025-15467.
AI and human contribution (source account): AISLE’s January 26, 2026 article says its autonomous analyzer found all 12 CVEs in OpenSSL’s January coordinated release, and individually names this case. OpenSSL’s own vulnerability record credits the named Aisle Research finder(s) for CVE-2025-15467; OpenSSL’s January 27 security advisory gives the flaw and report chronology. The exact model and division of AI versus researcher analysis are not public. OpenSSL credits Stanislav Fort (Aisle Research) as finder; AISLE’s article says its autonomous analyzer found all 12 CVEs in this release. The precise human/AI division is not published.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: OpenSSL published the vendor advisory and released fixes on January 27, 2026. The AISLE public AI attribution article appeared January 26, one day before the public vendor disclosure. No claim of in-the-wild exploitation is made.
Remediation status: fix documented. OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6 and 3.0.19. See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 27 Jan 2026. AI attribution dated 26 Jan 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Critical · highest recorded score 9.8. Documented technical effects: code execution, denial of service.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2025-15467: CVSS 3.1 · 8.8 (High) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. CISA-ADP (ADP; CVE Program record) · checked 16 Nov 2026. - CVE-2025-15467: CVSS 3.1 · 9.8 (Critical) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. redhat-SADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2025-15467: code execution, denial of service.
Prerequisites / affected scope: The CNA description states: 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..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6 and 3.0.19. See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.