llamaCVEVulnerability Intelligence
/
envoy

CVE-2026-73552

Envoy: HTTP RBAC safe_regex can fail open on RFC-valid obs-text header values

UnclearParche disponibleimproper input validation
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versiones1.36.10 · 1.37.6 · 1.38.4 · 1.39.1
Exposición58 dDesde la divulgación, 21 sept 2026, 2:37 p. m.
Detección56 dDesde 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.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV +1
21 sept 26
22 sept 26
17 nov 26
18 nov 26
19 nov 26
21 sept 26
6 oct 26
21 oct 26
4 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-73552 divulgada · CVSS 7.5 (CNA)
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy HTTP RBAC accepts RFC-valid opaque header bytes but evaluates safe_regex values with RE2's UTF-8 subject semantics. A downstream client can preserve a prohibited marker and add an unrelated obs-text octet, causing RE2::FullMatch to return false and a negative RBAC policy to treat the invalid subject as an ordinary no-match. A byte-oriented route matcher can still observe the marker, allowing the request to reach a route intended to be denied. The relevant scope boundary is that plain positive ALLOW regexes normally fail closed, and exact, prefix, suffix, and contains matchers are not shown to have this subject-domain failure. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Affects Envoy HTTP RBAC policies that apply safe_regex to header values with negative logic. Fixed in 1.36.10, 1.37.6, 1.38.4 and 1.39.1.

¿Qué significa?An HTTP RBAC safe_regex check on a header is applied to the complete field value, but a header can carry accepted non-UTF-8 obs-text bytes that RBAC fails to match. A negative policy can then let a client reach a protected resource, potentially disclosing protected data on the route.
¿Quién está afectado?The issue requires a negative header safe_regex policy, such as DENY with a positive regex or ALLOW with an inverted regex, plus a protected route or consumer that still reads the same header bytes byte-wise, such as a contains header matcher. Check the Envoy version in use and whether HTTP RBAC policies apply safe_regex to header values.
¿Qué hacer?Upgrade to Envoy 1.36.10, 1.37.6, 1.38.4, or 1.39.1, depending on the release line in use.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
A downstream-controlled HTTP header field can carry accepted non-UTF-8 obs-text bytes“a downstream-controlled HTTP field can contain accepted non-UTF-8 obs-text”
02
An HTTP RBAC policy applies safe_regex to the complete field value“an HTTP RBAC policy applies safe_regex to the complete field value;”
03
Authorization uses negative logic, such as DENY with a positive regex or ALLOW with an inverted regex condition“authorization uses negative logic, such as action: DENY with a positive regex or action: ALLOW with an inverted regex condition;”
04
A protected route or consumer still reads the same header bytes byte-wise, such as a contains header matcher“a protected operation remains reachable when another consumer still observes the preserved bytes that RBAC failed to match.”
¿Quién debe revisar?Teams running Envoy HTTP RBAC with negative safe_regex header rules (DENY, or ALLOW with inverted regex) on downstream-controlled headers
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
envoy< 1.36.10
envoy≥ 1.37.0 < 1.37.6
envoy≥ 1.38.0 < 1.38.4
envoy≥ 1.39.0 < 1.39.1
1.36.10
1.37.0
1.37.6
1.38.0
1.38.4
1.39.0
1.39.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
envoy
Corregida 1.36.10, 1.37.6, 1.38.4, 1.39.1 — —
Versiones corregidas1.36.101.37.61.38.41.39.1
Explotación

Arsenal público

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

Referencias
Fabricantehttps://github.com/envoyproxy/envoy/security/advisories/GHSA-23xh-2qxr-3xv8
Otrahttps://github.com/envoyproxy/envoy/commit/5650cb9770d4420ec2bcbed8b90be06f564ecc07
Otrahttps://github.com/envoyproxy/envoy/commit/7d1dee5dda66434d84437cc5c85153aa03955e26
Otrahttps://github.com/envoyproxy/envoy/commit/c2b9a19dc081f03be6a9b4ca932673e5e7a33d18
Otrahttps://github.com/envoyproxy/envoy/commit/f3726765f3a12ddc76dcb52c0b79bec3d95ced1c
Otrahttps://github.com/envoyproxy/envoy/releases/tag/v1.36.10
Otrahttps://github.com/envoyproxy/envoy/releases/tag/v1.37.6
Otrahttps://github.com/envoyproxy/envoy/releases/tag/v1.38.4
Otrahttps://github.com/envoyproxy/envoy/releases/tag/v1.39.1

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