Answer in brief
CVE-2026-53719 records a Medium severity (CVSS 6.5) vulnerability in Envoy Gateway: Nil-dereference when SecurityPolicy targets TCPRoute without spec.authorization. The current sources do not mark it as known exploited. The current feed maps envoyproxy/gateway (generic), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps envoyproxy/gateway (generic), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| envoyproxy/gatewaygeneric | < 1.7.4 || >= 1.8.0-rc.0, < 1.8.1 | Not reported |
| github.com/envoyproxy/gatewaygo | >=1.8.0-rc.0,<1.8.1 | 1.8.1 |
| github.com/envoyproxy/gatewaygo | <1.7.4 | 1.7.4 |
| github.com/envoyproxy/gatewaygo | >=1.8.0-rc.0 <1.8.1 | 1.8.1 |
| github.com/envoyproxy/gatewaygo | >=0 <1.7.4 | 1.7.4 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 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, 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.
Quoted source text, attributed separately from HOL analysis.