cve.bz

CVE-2026-73548 envoyproxy envoy: HTTP Request Smuggling

7.5 highExploit referenceEPSS 0.5%Fix available

High (7.5) in envoyproxy envoy. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy forwards data for a configured non-WebSocket HTTP upgrade before the upstream accepts the upgrade. An unauthenticated HTTP/2 client can place a complete HTTP/1.1 request in extended CONNECT data; Envoy downgrades the request, writes the data unframed to a keep-alive HTTP/1.1 upstream, and returns the socket to the shared pool while the smuggled response remains queued. A different downstream client can then receive the attacker's response. The relevant scope boundary is that webSocket upgrades, plain CONNECT, disabled backend keep-alive, per-downstream pools, and max_requests_per_connection set to 1 are not affected by the demonstrated path. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-73548 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73548?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73548?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-73548 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-73548

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-73548](https://cve.bz/cve/badge/CVE-2026-73548.svg)](https://cve.bz/cve/CVE-2026-73548)

HTML:

<a href="https://cve.bz/cve/CVE-2026-73548"><img src="https://cve.bz/cve/badge/CVE-2026-73548.svg" alt="CVE-2026-73548"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
envoyproxy:envoybefore 1.36.10
envoyproxy:envoyfrom 1.37.0 before 1.37.6
envoyproxy:envoyfrom 1.38.0 before 1.38.4
envoyproxy:envoyfrom 1.39.0 before 1.39.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedistioctl1.30.4-1.1openSUSE-SU-2026:11630-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because an unauthenticated remote client can poison shared upstream connections, leading to cross-user response disclosure without requiring user privileges. OpenShift Service Mesh proxies (istio-proxy) and Envoy deployments are susceptible when configured to route generic, non-WebSocket HTTP upgrade requests toward HTTP/1.1 upstreams with connection reuse enabled. Standard HTTP operations and WebSocket upgrades remain unaffected, confining exposure to configurations utilizing custom protocol upgrades.

Red Hat's mitigation

To mitigate this issue:

1. Remove generic, non-WebSocket HTTP upgrade configurations from routes or listeners if custom protocol upgrades are not required.

2. If generic HTTP upgrades are necessary, prevent upstream connection reuse by configuring `max_requests_per_connection: 1` on the affected upstream cluster. In OpenShift Service Mesh, configure an Istio DestinationRule for the target service:

```yaml

apiVersion: networking.istio.io/v1beta1

kind: DestinationRule

metadata:

name: disable-connection-reuse

spec:

host: <target-service>

trafficPolicy:

connectionPool:

http:

maxRequestsPerConnection: 1

```

For standalone Envoy instances, define the setting under the upstream cluster configuration:

```yaml

clusters:

- name: <upstream-cluster>

max_requests_per_connection: 1

```

Caveats: Setting maximum requests per connection to 1 terminates connections after a single transaction, which can increase latency and CPU utilization on proxies and backends due to repeated connection handshakes.

Warning: Modifying proxy configurations will initiate a configuration reload and may require restarting proxy pods to flush and terminate existing upstream connection pools.

ProductPackageStateAdvisory
Red Hat OpenShift Service Mesh 3.0openshift-service-mesh/istio-proxyv2-rhel9:1788296328Fixed 2026-09-08RHSA-2026:65106
Red Hat OpenShift Service Mesh 3.1openshift-service-mesh/istio-proxyv2-rhel9:1788294715Fixed 2026-09-08RHSA-2026:65112
Red Hat OpenShift Service Mesh 3.2openshift-service-mesh/istio-proxyv2-rhel9:1788329366Fixed 2026-09-08RHSA-2026:65113
Red Hat OpenShift Service Mesh 3.3openshift-service-mesh/istio-proxyv2-rhel9:1788327866Fixed 2026-09-08RHSA-2026:65115
Red Hat OpenShift Service Mesh 3.4openshift-service-mesh/istio-proxyv2-rhel9:1788333924Fixed 2026-09-08RHSA-2026:65121

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-73548.

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON