LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39156: Fragments in Path May Lead to Authorization Policy Bypass

Istio is an open source platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio 1.11.0, 1.10.3 and below, and 1.9.7 and below contain a remotely exploitable vulnerability where an HTTP request with `#fragment` in the path may bypass Istio’s URI path based authorization policies. Patches are available in Istio 1.11.1, Istio 1.10.4 and Istio 1.9.8. As a work around a Lua filter may be written to normalize the path.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Affected Istio versions could let a specially formed HTTP path bypass path-based authorization rules. For organizations relying on Istio to restrict access between services or public routes, this can expose protected data or functions without compromising credentials.

Executive priority

Treat as high priority where Istio enforces access to sensitive APIs or public ingress routes. Patch quickly, because successful bypass can undermine intended authorization controls.

Technical view

Istio 1.11.0, 1.10.3 and below, and 1.9.7 and below mishandle HTTP paths containing a fragment marker, allowing bypass of URI path based authorization policies. The CVE is CWE-863 with CVSS 8.1. Fixed releases are 1.11.1, 1.10.4, and 1.9.8.

Likely exposure

Exposure is most likely in Kubernetes or microservice environments using affected Istio releases and AuthorizationPolicy rules that depend on URI path matching.

Exploitation context

The bundle describes remote exploitability and high confidentiality and integrity impact. It does not cite KEV listing or public active exploitation evidence.

Researcher notes

Evidence supports an authorization bypass tied specifically to URI path based policies. The source bundle names patched versions and a Lua normalization workaround, but does not provide active exploitation evidence.

Mitigation direction

  • Upgrade Istio to 1.11.1, 1.10.4, 1.9.8, or later supported releases.
  • Use the vendor-described Lua path normalization workaround if immediate upgrade is not possible.
  • Review Istio authorization policies that rely on URI path matching.
  • Check current Istio vendor guidance before applying operational workarounds.
  • Prioritize internet-facing gateways and sensitive service-to-service authorization boundaries.

Validation and detection

  • Inventory Istio control plane and data plane versions across clusters.
  • Identify AuthorizationPolicy rules that use path or URI based matching.
  • Confirm all affected clusters are upgraded to patched Istio releases.
  • Run controlled regression tests for protected routes with fragment-like path cases.
  • Review access logs for unexpected successful requests to protected paths.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-39156 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2021-39156Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
istioistio< 1.9.8, >= 1.10.0, < 1.10.4, >= 1.11.0, < 1.11.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.