Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-53715: 0.47% estimated exploitation activity in the next 30 days; percentile 40.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability report without repro case. Repro case may be added later after harness is complete. Preconditions (4): - Pod-network reachability to :18002 (no auth) - Tenant can create EnvoyExtensionPolicy (baseline) - Attacker pod floods GET while churning EnvoyExtensionPolicy with distinct Wasm URLs - Read at :153 must overlap a write at :201/:209 (probabilistic, attacker controls both rates) Description: httpserver.go:153 reads s.mappingPath2Cache with no lock while httpserver.go:201/209 write it under s.Lock(); the struct uses a plain map. Writer is tenant-reachable via EnvoyExtensionPolicy translation, reader is pod-network-reachable on :18002 with per-request goroutines. Go's concurrent map read+write detection calls runtime.throw, which net/http's per-conn recover cannot catch, so the controller process exits — cross-tenant control-plane DoS. Capped at MEDIUM: DoS-only, k8s restarts pod, timing-dependent trigger.

Published by the source

16 Jul 2026, 19:21 UTC

Last modified by the source

16 Jul 2026, 19:21 UTC

Source last checked

26 Oct 2026, 15:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8fv2-88gg-hm7q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53715

Advisory: Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock
IDs: CVE-2026-53715, GHSA-8fv2-88gg-hm7q
Record: https://patchnext.com/advisories/cve-2026-53715 (revision 1, source checked 26 Oct 2026, 15:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/envoyproxy/gateway 1.8.1, 1.7.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/envoyproxy/gateway: affected >= 1.8.0-rc.0, < 1.8.1; < 1.7.4; fixed in 1.8.1, 1.7.4

## Suggested inspection (read-only)
- Go github.com/envoyproxy/gateway: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/envoyproxy/gateway.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8fv2-88gg-hm7q (GitHub-reviewed advisory GHSA-8fv2-88gg-hm7q lists affected ranges: Go github.com/envoyproxy/gateway >=1.8.0-rc.0 =0 <1.7.4)

Commands are suggestions: review each one before running it.