CVE-2026-53719: envoyproxy gateway · NULL Pointer Dereference
Affects envoyproxy gatewaySource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.8.1 or 1.7.4 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.1, 1.7.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade gateway and envoyproxy/gateway to 1.8.1 or 1.7.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| envoyproxygateway | Affected
| Fixed in
|
| envoyproxygateway | Affected
| Fixed in
|
GitHubenvoyproxy/gatewaypkg:github/envoyproxy/gatewayOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This issue is fixed in Envoy Gateway versions 1.7.4 and 1.8.1. Users should upgrade to at least one of these versions to remediate the vulnerability. Until upgraded, administrators can mitigate the impact by deleting any SecurityPolicy objects that omit the spec.authorization field when targeting TCPRoute, preventing the panic and stalled publishing.
Description
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, translateSecurityPolicyForRoute in internal/gatewayapi/securitypolicy.go dereferences a nil authorization value when a namespace-scoped tenant creates a SecurityPolicy targeting a TCPRoute and omits spec.authorization. The persistent object triggers the panic on every reconcile; recovery in message/watchutil.go keeps the process alive but unwinds the runner/runner.go handle callback, stalling controller-wide xDS and infrastructure intermediate-representation publishing until an administrator deletes the object. The data plane continues to serve the last known good configuration while publication is stalled. This issue is fixed in versions 1.7.4 and 1.8.1.
References
- github.com/envoyproxy/gateway/security/advisories/GHSA-m2v6-2jmh-4c68 (opens in a new tab)
- github.com/envoyproxy/gateway/pull/9171 (opens in a new tab)
- github.com/envoyproxy/gateway/pull/9172 (opens in a new tab)
- github.com/envoyproxy/gateway/pull/9173 (opens in a new tab)
- github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464 (opens in a new tab)
- github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7 (opens in a new tab)
- github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead (opens in a new tab)
- github.com/envoyproxy/gateway/releases/tag/v1.7.4 (opens in a new tab)
- github.com/envoyproxy/gateway/releases/tag/v1.8.1 (opens in a new tab)