Is CVE-2026-53713 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53713 being exploited in the wild.

How severe is CVE-2026-53713?

Critical severity, with a CVSS score of 9.1, published 14 September 2026.

Which products and versions are affected?

github.com/envoyproxy/gateway (Go) SEMVER:introduced=0,fixed=1.7.4,introduced=1.8.0-rc.0,fixed=1.8.1, SEMVER:introduced=1.8.0-rc.0,fixed=1.8.1.

Is there a fix for CVE-2026-53713?

Yes. github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53713 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53713?

Check whether you run github.com/envoyproxy/gateway (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53713: Envoy Gateway authentication bypass in EnvoyExtensionPolicy Lua

CVE-2026-53713 · Severity: critical · CVSS 9.1 · Published 2026-09-14

Envoy Gateway is a tool used to manage network traffic and security policies for applications. A vulnerability in its Lua extension policy allows an attacker with basic permissions to bypass security checks and read sensitive files from the system. This could lead to the theft of Kubernetes service tokens, TLS certificates, and other credentials, potentially allowing an attacker to gain broader control over the cloud environment.

Technologies: github.com/envoyproxy/gateway (Go). Vendors: Go.

Quick answers

Is CVE-2026-53713 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53713 being exploited in the wild.
How severe is CVE-2026-53713?: Critical severity, with a CVSS score of 9.1, published 14 September 2026.
Which products and versions are affected?: github.com/envoyproxy/gateway (Go) SEMVER:introduced=0,fixed=1.7.4,introduced=1.8.0-rc.0,fixed=1.8.1, SEMVER:introduced=1.8.0-rc.0,fixed=1.8.1.
Is there a fix for CVE-2026-53713?: Yes. github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53713 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53713?: Check whether you run github.com/envoyproxy/gateway (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later
```
go get github.com/envoyproxy/gateway@v1.8.1
```

Technical details

An authentication bypass exists in Envoy Gateway's EnvoyExtensionPolicy due to improper input validation in the Lua 'to_absolute_normalized_path' function. The function fails to collapse redundant path separators (e.g., '//'), which allows attackers to bypass 'is_critical_path' checks that only look for single-slash prefixes like '/etc/'. By submitting malicious Lua code via an EnvoyExtensionPolicy, a remote attacker with low privileges can perform an arbitrary file read on the gateway controller pod's filesystem. This can be used to disclose Kubernetes SA tokens, TLS certificates, and process environment variables. The issue is fixed in versions 1.7.4 and 1.8.1 by ensuring path normalization collapses separators and rejecting directory traversal segments.

Affected products

envoyproxy gateway < 1.7.4, >= 1.8.0-rc.0, < 1.8.1

Identifiers

CVE-2026-53713
GHSA-wcrf-9vrr-854f
GO-2026-6011

Timeline

2026-06-05: disclosed
2026-07-16: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.