NVD / CVE Program· CNA openssl

CVE-2026-45446: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes

Noroxi assessment

Priority: Monitor (action score 19/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: OpenSSL OpenSSL 3.0.21, 3.4.6, 3.5.7; azl3 openssl 3.3.5-5 on Azure Linux 3.0 3.3.7-3.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.21, 3.4.6, 3.5.7; azl3 openssl 3.3.5-5 on Azure Linux 3.0 3.3.7-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Issue summary: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update, which can happen when the received ciphertext length is zero, the tag is never recalculated and still holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not FIPS approved and the affected code is outside the OpenSSL FIPS module boundary.

MediumCVSS 4.8 · v3.1—No exploit Fix available

Pre-auth

Published: Jun 9, 2026
Updated: Jul 23, 2026
EPSS: 0.4% · 38th percentile
CWE: CWE-325

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 19 / 40 · 4.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
openssl	openssl	cpe:2.3:a:openssl:openssl

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

openssl openssl3.0.0 and later · before 3.0.21
openssl openssl3.4.0 and later · before 3.4.6
openssl openssl3.5.0 and later · before 3.5.7
openssl openssl3.6.0 and later · before 3.6.3
openssl openssl4.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

OpenSSL OpenSSL
- 4.0.0 and later · before 4.0.1affected · semver
- 3.6.0 and later · before 3.6.3affected · semver
- 3.5.0 and later · before 3.5.7affected · semver
- 3.4.0 and later · before 3.4.6affected · semver
- 3.0.0 and later · before 3.0.21affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	openssl	before 1:3.5.5-4.el10_2.alma.1	1:3.5.5-4.el10_2.alma.1
AlmaLinux:10	openssl-devel	before 1:3.5.5-4.el10_2.alma.1	1:3.5.5-4.el10_2.alma.1
AlmaLinux:10	openssl-libs	before 1:3.5.5-4.el10_2.alma.1	1:3.5.5-4.el10_2.alma.1
AlmaLinux:10	openssl-perl	before 1:3.5.5-4.el10_2.alma.1	1:3.5.5-4.el10_2.alma.1
AlmaLinux:9	openssl	before 1:3.5.5-4.el9_8	1:3.5.5-4.el9_8
AlmaLinux:9	openssl-devel	before 1:3.5.5-4.el9_8	1:3.5.5-4.el9_8
AlmaLinux:9	openssl-libs	before 1:3.5.5-4.el9_8	1:3.5.5-4.el9_8
AlmaLinux:9	openssl-perl	before 1:3.5.5-4.el9_8	1:3.5.5-4.el9_8
Alpine:v3.21	openssl	from 3.0.0 · before 3.3.7-r1	3.3.7-r1
Alpine:v3.22	openssl	from 3.0.0 · before 3.5.7-r0	3.5.7-r0
Debian:12	openssl	before 3.0.20-1~deb12u2	3.0.20-1~deb12u2
Debian:13	openssl	before 3.5.6-1~deb13u2	3.5.6-1~deb13u2
Debian:14	openssl	before 3.6.3-1	3.6.3-1
openSUSE:Leap 16.0	openssl-3	before 3.5.0-160000.8.1	3.5.0-160000.8.1
openSUSE:Tumbleweed	openssl-3	before 3.5.3-6.1	3.5.3-6.1
Red Hat:enterprise_linux:10.2	openssl	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:10.2	openssl-debuginfo	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:10.2	openssl-debugsource	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:10.2	openssl-devel	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:10.2	openssl-libs	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:10.2	openssl-libs-debuginfo	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:10.2	openssl-perl	before 1:3.5.5-4.el10_2	1:3.5.5-4.el10_2
Red Hat:enterprise_linux:9::appstream	openssl-debuginfo	before 1:3.5.5-4.el9_8	1:3.5.5-4.el9_8
Red Hat:enterprise_linux:9::appstream	openssl-debugsource	before 1:3.5.5-4.el9_8	1:3.5.5-4.el9_8

+84

Same product

openssl: all records

Other highest-scoring records for the same primary product.

CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
90Now
CVE-2021-3711SM2 Decryption Buffer Overflow
65This week
CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
65This week

Published before and after this one in the same product

← EarlierCVE-2026-42771Jun 9, 2026 · Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email()
24Monitor
← EarlierCVE-2026-45445Jun 9, 2026 · AES-OCB IV Ignored on EVP_Cipher() Path
30Monitor
Later →CVE-2026-45447Jun 9, 2026 · Heap Use-After-Free in the PKCS7_verify() Function
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
OpenSSL OpenSSL	3.0.21	Vendor (CNA)
OpenSSL OpenSSL	3.4.6	Vendor (CNA)
OpenSSL OpenSSL	3.5.7	Vendor (CNA)
OpenSSL OpenSSL	3.6.3	Vendor (CNA)
OpenSSL OpenSSL	4.0.1	Vendor (CNA)
azl3 openssl 3.3.5-5 on Azure Linux 3.0	3.3.7-3 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:openssl	1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10	Package registry (OSV)
almalinux:openssl-devel	1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10	Package registry (OSV)
almalinux:openssl-libs	1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10	Package registry (OSV)
almalinux:openssl-perl	1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10	Package registry (OSV)
alpine:openssl	3.3.7-r1 · Alpine:v3.21	Package registry (OSV)
debian:openssl	3.0.20-1~deb12u2 · Debian:12	Package registry (OSV)
opensuse:openssl-3	3.5.3-6.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:chunkah	0:0.6.0-3.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssl	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl-debuginfo	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl-debugsource	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl-devel	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl-libs	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl-libs-debuginfo	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl-perl	1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:openssl3	0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssl3-devel	0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:python-cryptography	0:50.0.0-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:python3-cryptography	0:50.0.0-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
rocky linux:openssl	1:3.5.5-4.el10_2 · Rocky Linux:10	Package registry (OSV)
suse:openssl-3	3.1.4-14.1 · SUSE:Linux Micro 6.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Alex Gaynor (Anthropic)reporter
Dmitry Belyavskiy (Red Hat)remediation developer

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-454450 days apartAES-OCB IV Ignored on EVP_Cipher() Path
30Monitor
CVE-2025-69418133 days apartUnauthenticated/unencrypted trailing bytes with low-level OCB function calls
16Monitor
CVE-2026-427700 days apartFFC-DH Peer Validation Uses Attacker-Supplied q
14Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).