CVE-2026-45447

Published Jun 9, 2026

Last updated 18 days ago

CVSS high 8.8
Ubuntu
SSL
Port (443)

Overview

AI description

Automated description summarized from trusted sources.

CVE-2026-45447 describes a heap use-after-free vulnerability found in OpenSSL's PKCS7_verify() function. This flaw can be triggered when OpenSSL processes a specially crafted PKCS#7 or S/MIME signed message. Specifically, if the SignedData digestAlgorithms field within such a message is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during the signature verification process. A subsequent attempt by the application to use the already freed BIO results in a use-after-free condition. This issue primarily affects applications that utilize OpenSSL's PKCS#7 APIs for processing PKCS#7 or S/MIME signed messages. Applications using the CMS APIs for this purpose are not impacted.

Description
Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition. In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution. Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Source
openssl-security@openssl.org
NVD status
Modified
Products
openssl

Risk scores

CVSS 3.1

Type
Secondary
Base score
8.8
Impact score
5.9
Exploitability score
2.8
Vector string
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

openssl-security@openssl.org
CWE-416
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
CWE-825

Social media

Hype score
Not currently trending
  1. ⚠️ Vulnerabilidades en productos OpenSSL ❗ CVE-2026-9076 ❗ CVE-2026-7383 ❗ CVE-2026-45447 ➡️ Más info: https://t.co/Gq3dW9TevE https://t.co/yaTVoQCWnH

    @CERTpy

    23 Jun 2026

    232 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. OpenSSL no openSUSE: 5 CVEs críticas (CVE-2026-45447, CVE-2026-42766, CVE-2026-9076, CVE-2026-7383, CVE-2026-34180). Saiba mais: -> https://t.co/CT6lCGzATz #openSUSE https://t.co/tRrkR6h5YK

    @Cezar_H_Linux

    16 Jun 2026

    40 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    1 Reply

    0 Quotes

  3. AIを使う側が、狙われる番に回った。 開発を支えるAIツールと暗号・監視の土台が同じ日に穴を突かれ、足元の国内では教育と子どもの情報が漏れた。 ・OpenSSLにCVE-2026-45447、解放後使用の高危険度脆弱性をCla

    @boss_sec_labo

    14 Jun 2026

    2905 Impressions

    5 Retweets

    25 Likes

    11 Bookmarks

    0 Replies

    0 Quotes

  4. 何十年も専門家のレビューをくぐり抜けてきた脆弱性を、AIが掘り起こし始めました。 2026年6月9日、OpenSSLプロジェクトが高危険度の脆弱性「CVE-2026-45447」を含む計18件の脆弱性を公表し、修正版を公開しまし

    @TrinityDox_JP

    12 Jun 2026

    202 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  5. OpenSSL patches 16 flaws: CVE-2026-45447, heap use-after-free in PKCS7_verify() with RCE potential via crafted S/MIME. Also: unauthenticated QUIC DoS (CVE-2026-34183) and key forgery (CVE-2026-34182). Check static builds. https://t.co/k5NcivCF2t #CyberSecu https://t.co/nC2CFxcNTX

    @securitydailyr

    11 Jun 2026

    41 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.•CVE-2026-84782

References

Sources include official advisories and independent security research.