github.com/envoyproxy/gateway
Affected
- introduced
1.8.0-rc.0, fixed1.8.1(semver)
Fixed versions
1.8.1
Fix
- Fixed version
1.8.1go get github.com/envoyproxy/[email protected]
Advisory
Also known as: BIT-envoy-gateway-2026-53713, CVE-2026-53713, GO-2026-6011
Envoy Gateway: Authentication Bypass via Improper Input Validation in EnvoyExtensionPolicy Lua Allows Secret Disclosure
Impact
The to_absolute_normalized_path function (security.lua:28-43) does not collapse redundant path separators (// → /). On Linux, //etc/passwd is equivalent to /etc/passwd (POSIX path semantics), but is_critical_path fails to match the double-slash variant because //etc/passwd does not start with /etc/.
This allows Lua code submitted as an EnvoyExtensionPolicy to read arbitrary files from the gateway controller pod's filesystem during Strict validation (the default), including:
/etc/passwd//var/run/secrets/kubernetes.io/serviceaccount/token//certs/...//proc/self/environThese credentials can be used to read sensitive information from the K8s API Server or from the Gateway XDS server.
Patches
This has been patched in versions >= v1.7.4 and v1.8.1
// to /) so double-slash variants like //etc/passwd and //var/run/secrets/... are matched by the critical-path check.. or .. segment in any position and across both separator styles (catches /etc/./passwd, ./etc/passwd, /etc/.).Workarounds
Please refer to the Warning section in Lua docs for measures to reduce risk.
Credits
Envoy Gateway thanks @dashingDragon and @Donjon-Cerberus for reporting this issue.
Critical Basis: The source's own band: CRITICAL
1.8.0-rc.0, fixed 1.8.1 (semver)1.8.1
1.8.1go get github.com/envoyproxy/[email protected]0, fixed 1.7.4 (semver)1.7.4
1.7.4go get github.com/envoyproxy/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0