Is CVE-2026-53719 exploited in the wild?

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

How severe is CVE-2026-53719?

Medium severity, with a CVSS score of 6.5, 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-53719?

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-53719 attacked?

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

Am I affected by CVE-2026-53719?

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-53719: Envoy Gateway NULL pointer dereference in SecurityPolicy

CVE-2026-53719 · Severity: medium · CVSS 6.5 · Published 2026-09-14

Envoy Gateway is a tool used to manage network traffic for cloud-native applications. A vulnerability exists where a user with limited permissions can crash the management component by providing a specific configuration that is missing required authorization details. While existing network traffic continues to flow, this crash prevents administrators from making any further updates or changes to the network configuration until the problematic entry is manually removed.

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

Quick answers

Is CVE-2026-53719 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53719 being exploited in the wild.
How severe is CVE-2026-53719?: Medium severity, with a CVSS score of 6.5, 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-53719?: 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-53719 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53719?: 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

A NULL pointer dereference (CWE-476) exists in Envoy Gateway's gatewayapi runner. When a SecurityPolicy targets a TCPRoute and the 'spec.authorization' field is omitted, the reconcile process triggers a panic. While a recovery mechanism prevents the entire process from exiting, it unwinds the handle() callback, effectively stalling xDS and Infrastructure Intermediate Representation (IR) publishing controller-wide. This allows a namespace-scoped tenant with permissions to create these resources to deterministically block all configuration updates. The issue is fixed in versions 1.7.4 and 1.8.1.

Affected products

Envoy Proxy Envoy Gateway >= 1.8.0-rc.0, < 1.8.1; < 1.7.4

Identifiers

CVE-2026-53719
GHSA-m2v6-2jmh-4c68
GO-2026-6009

Timeline

2026-06-05: disclosed
2026-07-16: advisory
2026-07-16: patched

References

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