Skip to content
Sign in
CVE-2026-88823Not scoredCWE-325

CVE-2026-88823

Vendor not yet named

No distribution fix yet for Debian 12/13, SLES 15 SP7/16.0/16.1, openSUSE Leap 16.0/16.1 · Exploitation: not established

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.10 (10 Nov)

  1. In CISA KEV: not seen
  2. Exploited (reported): not seen
  3. Scanning observed: not seen
  4. Proof of concept public: not seen
  5. Not establishedNothing in the sources we check

No EPSS score yet. The score appears once FIRST publishes it.

Not scored yet. NVD has not published a CVSS score.

DescriptionNVD

Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary.

Fix status by distribution

From each distribution’s security tracker. Distributions we did not check are not listed.

What changed

Debian status tracked since 10 Nov 2026. SUSE status tracked since 10 Nov 2026.

  1. Debian’s tracker lists Debian 12 as affected, with no fix released Debian
  2. Debian’s tracker lists Debian 13 as affected, with no fix released Debian
  3. SUSE’s tracker lists openSUSE Leap 16.0 as affected, with no fix released SUSE
  4. SUSE’s tracker lists openSUSE Leap 16.1 as affected, with no fix released SUSE
  5. SUSE’s tracker lists SLES 12 SP5 as not affected SUSE
  6. SUSE’s tracker lists SLES 15 SP1 as not affected SUSE
  7. SUSE’s tracker lists SLES 15 SP2 as not affected SUSE
  8. SUSE’s tracker lists SLES 15 SP3 as not affected SUSE
  9. SUSE’s tracker lists SLES 15 SP4 as not affected SUSE
  10. SUSE’s tracker lists SLES 15 SP5 as not affected SUSE
  11. SUSE’s tracker lists SLES 15 SP6 as not affected SUSE
  12. SUSE’s tracker lists SLES 15 SP7 as affected, with no fix released SUSE
  13. SUSE’s tracker lists SLES 16.0 as affected, with no fix released SUSE
  14. SUSE’s tracker lists SLES 16.1 as affected, with no fix released SUSE

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 10 Nov.

  1. OpenSSL details five low severity flaws across its products
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References

CyberSIXTSignal over noise
Updated AboutDevelopersSign in