---
title: "CVE-2026-53713: Envoy Gateway - Path Traversal"
description: "Envoy Gateway < 1.7.4 and < 1.8.1 contains a file system read caused by improper path normalization in to_absolute_normalized_path in internal/gatewayapi/luavalidator/security.lua, letting attackers read arbitrary files from the gateway controller pod, exploit requires submission of Lua code through EnvoyExtensionPolicy."
url: https://panop.io/threat-heartbeat/CVE-2026-53713/
---

# CVE-2026-53713 Envoy Gateway - Path Traversal

Envoy Gateway < 1.7.4 and < 1.8.1 contains a file system read caused by improper path normalization in to\_absolute\_normalized\_path in internal/gatewayapi/luavalidator/security.lua, letting attackers read arbitrary files from the gateway controller pod, exploit requires submission of Lua code through EnvoyExtensionPolicy.

CVSS base score 9.1 /10

Critical

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.43% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-53713)

## Details

Type

Path Traversal

Impact

File System Read, Information Disclosure

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

Published

14 September 2026

Updated

15 October 2026

Weakness

[CWE-20](https://cwe.mitre.org/data/definitions/20.html)

## Vendor fix

Update to versions 1.7.4 and 1.8.1 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-53713](https://nvd.nist.gov/vuln/detail/CVE-2026-53713)
- [https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464](https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464)
- [https://github.com/envoyproxy/gateway/pull/9171](https://github.com/envoyproxy/gateway/pull/9171)
- [https://github.com/envoyproxy/gateway/pull/9173](https://github.com/envoyproxy/gateway/pull/9173)
- [https://github.com/envoyproxy/gateway/releases/tag/v1.7.4](https://github.com/envoyproxy/gateway/releases/tag/v1.7.4)
- [https://github.com/envoyproxy/gateway/releases/tag/v1.8.1](https://github.com/envoyproxy/gateway/releases/tag/v1.8.1)
- [https://github.com/envoyproxy/gateway/security/advisories/GHSA-wcrf-9vrr-854f](https://github.com/envoyproxy/gateway/security/advisories/GHSA-wcrf-9vrr-854f)
- [https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7](https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7)
- [https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead](https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead)
- [https://github.com/envoyproxy/gateway/pull/9172](https://github.com/envoyproxy/gateway/pull/9172)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)