CVE-2026-53713

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, to_absolute_normalized_path in internal/gatewayapi/luavalidator/security.lua does not collapse redundant separators before is_critical_path evaluates Lua submitted through EnvoyExtensionPolicy during default Strict validation. Linux resolves a double-slash absolute path as the corresponding single-slash path, but the validator does not match the redundant-separator form, allowing submitted Lua to read arbitrary files from the gateway controller pod. Exposed files can include Kubernetes service-account tokens, TLS certificates, and process environment data, and the disclosed credentials can provide access to sensitive Kubernetes API Server or Gateway xDS server information. This issue is fixed in versions 1.7.4 and 1.8.1.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

July 16, 2026

Last Modified

September 16, 2026

Advisory Details (9)

Auto-updated Sep 15, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available

Authentication Bypass via Improper Input Validation in EnvoyExtensionPolicy Lua Allows Secret Disclosure · Advisory · envoyproxy/gateway · GitHub

Affected: versions >= v1.7.4 and v1.8.1

https://github.com/envoyproxy/gateway/security/advisories/GHSA-wcrf-9vrr-854f
github_release Patch Available

v1.8.1

Patch available: envoyproxy/gateway v1.8.1

https://github.com/envoyproxy/gateway/releases/tag/v1.8.1
github_release Patch Available

v1.7.4

Patch available: envoyproxy/gateway v1.7.4

https://github.com/envoyproxy/gateway/releases/tag/v1.7.4
github_pr

fix github SA for June release

Fix merged in envoyproxy/gateway PR #9173 on 2026-06-05 — awaiting tagged release

https://github.com/envoyproxy/gateway/pull/9173
github_pr

[release-1.8] fix github SA for June release

Fix merged in envoyproxy/gateway PR #9172 on 2026-06-05 — awaiting tagged release

https://github.com/envoyproxy/gateway/pull/9172
github_pr

[release-1.7] fix github SA for June release

Fix merged in envoyproxy/gateway PR #9171 on 2026-06-05 — awaiting tagged release

https://github.com/envoyproxy/gateway/pull/9171
github_commit

commit b4737180c7e5 (envoyproxy/gateway)

Fix landed in envoyproxy/gateway commit b4737180c7e5 — awaiting tagged release

https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead
github_commit

commit 96e2b750868a (envoyproxy/gateway)

Fix landed in envoyproxy/gateway commit 96e2b750868a — awaiting tagged release

https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7
github_commit

commit 5a78db82b7cf (envoyproxy/gateway)

Fix landed in envoyproxy/gateway commit 5a78db82b7cf — awaiting tagged release

https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464

Vendor Advisories for CVE-2026-53713(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/envoyproxy/gateway—1.8.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:38 UTCEG score recompute
  3. 2026-09-16 19:26 UTCEG score recompute
  4. 2026-09-16 18:41 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 21:33 UTCEG score recompute
  8. 2026-07-30 13:05 UTCEG score recompute
  9. 2026-07-26 11:25 UTCEG score recompute
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-16 20:04 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53713?
CVE-2026-53713 is a critical vulnerability published on July 16, 2026. Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, toabsolutenormalizedpath in internal/gatewayapi/luavalidator/security.lua does not collapse redundant separators before iscritical_path evaluates Lua…
When was CVE-2026-53713 disclosed?
CVE-2026-53713 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53713 actively exploited?
CVE-2026-53713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53713?
CVE-2026-53713 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-53713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53713, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53713

Explore →

Is Your Infrastructure Affected by CVE-2026-53713?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs