Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-45446

openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes

Overview

Published
9 Jun 2026
Modified
23 Jul 2026
Medium CVE
3 Registry packages
45 OS packages
21 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

4.8 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Weakness: CWE-325

Affected packages · 3

Packages affected by CVE-2026-45446
EcosystemPackageVulnerableFixed in
Julia AppBundler >=1.0.0, <1.0.1 1.0.1
Julia Openresty_jll >=1.27.1+0 No fix yet
Julia OpenSSL_jll >=3.0.8+0, <3.5.7+0 3.5.7+0

Open a package to see all its vulnerabilities.

Operating systems · 62 fixes

Azure Linux 1 release · 1 package

fixed 1
openssl
Azure Linux fixes for CVE-2026-45446
ReleasePackageFixed in
3.0 openssl 0:3.3.7-3.azl3

Oracle Linux 1 release · 1 package

fixed 2
openssl
Oracle Linux fixes for CVE-2026-45446
ReleasePackageFixed in
9 openssl +3 10:3.5.5-4.0.1.el9_8_fips
9 openssl +3 1:3.5.5-4.0.1.el9_8

Photon OS 2 releases · 1 package

fixed 2
openssl
Photon OS fixes for CVE-2026-45446
ReleasePackageFixed in
4.0 openssl +4 3.0.21-1.ph4
5.0 openssl +5 3.5.7-1.ph5

Red Hat 3 releases · 3 packages

affected 3 fixed 1
openshift-ose-rhel-coreos-8 compat-openssl11 openssl
Red Hat fixes for CVE-2026-45446
ReleasePackageFixed inAdvisory
7 openshift-ose-rhel-coreos-8 +1 affected —
8 openshift-ose-rhel-coreos-8 +1 affected —
9 compat-openssl11 +12 affected —
9 openssl +3 1:3.5.5-4.el9_8 RHSA-2026:25239

SUSE Linux Enterprise 5 releases · 1 package

fixed 5
libopenssl-3-devel
SUSE Linux Enterprise fixes for CVE-2026-45446
ReleasePackageFixed inAdvisory
15.4 libopenssl-3-devel +2 3.0.8-150400.4.87.1 SUSE-SU-2026:2598-1
15.5 libopenssl-3-devel +2 3.0.8-150500.5.66.1 SUSE-SU-2026:2397-1
15.6 libopenssl-3-devel +5 3.1.4-150600.5.53.1 SUSE-SU-2026:2393-1
15.7 libopenssl-3-devel +5 3.2.3-150700.5.36.1 SUSE-SU-2026:2648-1
16.0 libopenssl-3-devel +6 3.5.0-160000.8.1 SUSE-SU-2026:22315-1

SUSE Linux Enterprise Micro 5 releases · 2 packages

fixed 5
libopenssl3 libopenssl-3-devel
SUSE Linux Enterprise Micro fixes for CVE-2026-45446
ReleasePackageFixed inAdvisory
5.3 libopenssl3 3.0.8-150400.4.87.1 SUSE-SU-2026:2598-1
5.4 libopenssl3 3.0.8-150400.4.87.1 SUSE-SU-2026:2598-1
6.0 libopenssl-3-devel +3 3.1.4-14.1 SUSE-SU-2026:22100-1
6.1 libopenssl-3-devel +3 3.1.4-slfo.1.1_10.1 SUSE-SU-2026:22132-1
6.2 libopenssl-3-devel +3 3.5.0-160000.8.1 SUSE-SU-2026:22251-1

alma 1 release · 1 package

fixed 1
openssl
alma fixes for CVE-2026-45446
ReleasePackageFixed in
9 openssl +3 1:3.5.5-4.el9_8

alpine 4 releases · 1 package

fixed 4
openssl
alpine fixes for CVE-2026-45446
ReleasePackageFixed in
3.22 openssl 3.5.7-r0
3.23 openssl 3.5.7-r0
3.24 openssl 3.5.7-r0
edge openssl 3.5.7-r0

amazon linux 1 release · 1 package

fixed 1
openssl
amazon linux fixes for CVE-2026-45446
ReleasePackageFixed in
2023 openssl +10 1:3.5.5-1.amzn2023.0.5

chainguard 1 release · 4 packages

not affected 1 fixed 3
openssl-provider-fips-3-4-0 openssl-3-5 libcrypto3-2-34 openssl-4-0
chainguard fixes for CVE-2026-45446
ReleasePackageFixed in
openssl-provider-fips-3-4-0 +1 not affected
openssl-3-5 3.5.7-r0
libcrypto3-2-34 +1 3.6.3-r0
openssl-4-0 4.0.1-r0

debian 3 releases · 1 package

fixed 3
openssl
debian fixes for CVE-2026-45446
ReleasePackageFixed in
12 openssl 3.0.20-1~deb12u2
13 openssl 3.5.6-1~deb13u2
14 openssl 3.6.3-1

echo 1 release · 4 packages

fixed 4
openssl openssl-3-0-9 openssl-3-1-0 openssl-3-5-0
echo fixes for CVE-2026-45446
ReleasePackageFixed in
openssl 3.0.20-1~deb12u2
openssl-3-0-9 3.0.9+e1
openssl-3-1-0 3.1.0+e1
openssl-3-5-0 3.5.0+e1

minimos 1 release · 2 packages

fixed 2
openssl-3-0 openssl
minimos fixes for CVE-2026-45446
ReleasePackageFixed in
openssl-3-0 3.0.21-r0
openssl 3.5.7-r0

openSUSE 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE fixes for CVE-2026-45446
ReleasePackageFixed inAdvisory
Tumbleweed libopenssl-3-devel +9 3.5.3-6.1 openSUSE-SU-2026:11023-1

openSUSE Leap 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE Leap fixes for CVE-2026-45446
ReleasePackageFixed inAdvisory
16.0 libopenssl-3-devel +6 3.5.0-160000.8.1 openSUSE-SU-2026:21005-1

rocky 2 releases · 1 package

fixed 2
openssl
rocky fixes for CVE-2026-45446
ReleasePackageFixed in
10 openssl +1 1:3.5.5-4.el10_2
9 openssl +1 1:3.5.5-4.el9_8

seal Red Hat 3 releases · 1 package

fixed 5
openssl
seal Red Hat fixes for CVE-2026-45446
ReleasePackageFixed in
7 openssl +1 1:1.0.2k-25.el7_9+sp999
7 openssl +1 1:1.0.2k-26.el7_9+sp999
8 openssl +1 1:1.1.1k-14.el8_6+sp999
8 openssl +1 1:1.1.1k-6.el8_5+sp999
9 openssl +1 1:3.2.2-6.el9_5+sp999

seal alpine 1 release · 2 packages

fixed 3
openssl seal-openssl
seal alpine fixes for CVE-2026-45446
ReleasePackageFixed in
openssl +1 3.3.2-r45341999
openssl 3.3.3-r0000
seal-openssl 3.3.3-r053413

seal debian 1 release · 1 package

fixed 6
openssl
seal debian fixes for CVE-2026-45446
ReleasePackageFixed in
openssl +1 3.0.11-1~deb12u2+sp999
openssl +1 3.0.13-0ubuntu3.4+sp999
openssl +1 3.0.16-1~deb12u1+sp999
openssl +1 3.0.2-0ubuntu1.19+sp999
openssl +1 3.0.2-0ubuntu1.20+sp999
openssl +1 3.5.4-1~deb13u1+sp999

ubuntu 3 releases · 2 packages

affected 1 fixed 3
nodejs openssl
ubuntu fixes for CVE-2026-45446
ReleasePackageFixed in
22.04 nodejs affected
22.04 openssl 3.0.2-0ubuntu1.25
24.04 openssl 3.0.13-0ubuntu3.11
26.04 openssl 3.5.5-1ubuntu3.2

wolfi 1 release · 2 packages

fixed 2
openssl openssl-4-0
wolfi fixes for CVE-2026-45446
ReleasePackageFixed in
openssl 3.6.3-r0
openssl-4-0 4.0.1-r0

References

Show all 68 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.