cve.bz

CVE-2026-73511 envoyproxy envoy: Authentication Bypass by Alternate Name

5.3 mediumExploit referenceEPSS 0.4%Fix available

Medium (5.3) in envoyproxy envoy. EPSS 0.4% 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 normally matches the raw request path, while servlet backends such as Apache Tomcat strip semicolon matrix parameters from each path segment before resolving the resource. Envoy's ignore_path_parameters_in_path_matching option instead truncates at the first semicolon and still does not match per-segment backend behavior. A remote client can use a parameterized protected segment, or a parameter on an earlier segment, to make Envoy select an unprotected fallback while the backend resolves the protected resource. The relevant scope boundary is that the bypass requires both a path-based Envoy decision and a backend that strips semicolon parameters per segment. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-289 Authentication Bypass by Alternate Name
CWE-436 Interpretation Conflict
OWASP Top 10
A06:2025 Insecure Design, A07:2025 Authentication Failures
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-73511 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73511?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73511?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-73511 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-73511

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-73511](https://cve.bz/cve/badge/CVE-2026-73511.svg)](https://cve.bz/cve/CVE-2026-73511)

HTML:

<a href="https://cve.bz/cve/CVE-2026-73511"><img src="https://cve.bz/cve/badge/CVE-2026-73511.svg" alt="CVE-2026-73511"></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 Moderate.

Red Hat's statement

This vulnerability is classified as having a Moderate severity for Red Hat OpenShift Service Mesh because successful exploitation depends on a specific architectural misalignment between proxy routing policies and backend path parsing, limiting the overall likelihood of exposure. A bypass can occur only when Envoy handles access control or routing based on URL paths while upstream services, such as servlet containers, independently strip semicolon-delimited matrix parameters from URI segments. Deployments utilizing token-based or identity-based authentication mechanisms, or applications that do not interpret matrix parameters, are not susceptible to this routing discrepancy.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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-73511.

Attack patterns (CAPEC)

  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting 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