llamaCVEVulnerability Intelligence
/
OpenSSL

CVE-2026-88823

OpenSSL forgery of AAD in AES-GCM-SIV after empty update

An attacker can forge additional authenticated data on messages protected after an empty AAD update.

Texto original en inglés · Ver en español

UnclearParche disponiblesecurity flaw
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Fuente: CISA-ADP
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versiones3.5.10 · 4.0.4 · 4.1.1
Exposición11 dDesde la divulgación, 10 nov 2026, 1:15 p. m.
Detección3 hDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Esto amerita una regla de detección, por si acaso.Seguimiento de cerca: yo sé de mirar de cerca.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
Verificada
10 nov 26
16 nov 26
21 nov 26
10 nov 26
13 nov 26
16 nov 26
19 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-88823 divulgada · CVSS 7.5 (CISA-ADP)
Monitoreo Detectada Ingresó al índice
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen

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.

Affects OpenSSL 3.5, 4.0 and 4.1 applications that supply AAD in several chunks with one zero-length chunk. No vendor rating is given, so only the CVSS score of 7.5 applies. Fixed in 4.1.1, 4.0.4 and 3.5.10.

¿Qué significa?On context re-initialisation after a zero-length incremental AAD update, AAD from earlier use is not reset and carries into the new message. Data the application meant to authenticate with that message is left unauthenticated, so an attacker can forge its AAD.
¿Quién está afectado?OpenSSL 3.5, 4.0 and 4.1 are affected, with the vendor's ranges fixed in 3.5.10, 4.0.4 and 4.1.1. The issue needs an application that supplies AAD in several chunks, one of them zero-length, and re-initialises the context. Check your version with the openssl version command.
¿Qué hacer?Upgrade to OpenSSL 4.1.1 on the 4.1 line, 4.0.4 on the 4.0 line, or 3.5.10 on the 3.5 line. The checked facts name no workaround.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Affected OpenSSL versions are 4.1, 4.0 and 3.5.“OpenSSL 4.1, 4.0, and 3.5 are vulnerable to this issue.”
02
Application supplies AAD in several chunks, one of which is zero-length.“several fragments, one of which is empty, therefore produces or verifies”
03
Context is re-initialised and AAD from earlier use carries over into the new message.“on context re-initialisation, the AAD was not reset, which meant that any AAD”
¿Quién debe revisar?Teams running OpenSSL 4.1, 4.0 or 3.5 that use AES-GCM-SIV with AAD supplied in several updates, some empty, or with reinitialised contexts.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CISA-ADP
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:N
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 10.0 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
OpenSSL≥ 3.5.0 < 3.5.10
OpenSSL≥ 4.0.0 < 4.0.4
OpenSSL≥ 4.1.0 < 4.1.1
3.5.0
3.5.10
4.0.0
4.0.4
4.1.0
4.1.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
OpenSSL
Corregida 3.5.10, 4.0.4, 4.1.1 — —
Versiones corregidas3.5.104.0.44.1.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://openssl-library.org/news/secadv/20261110.txt
Parchehttps://github.com/openssl/openssl/commit/6747b1a278816dd7db46438040a70b0b5e5e0a90
Parchehttps://github.com/openssl/openssl/commit/2f5fc833ff9b5bfe00b32f8b5c74f73c5773c682
Parchehttps://github.com/openssl/openssl/commit/159e1de0c448d7b9f09ad768c8e141def4aa1eb4

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.