Skip to content

AuthorizationPolicy conditions on request.headers[:authority] are bypassed by changing the host case

Moderate
fjglira published GHSA-7m6f-j3gp-2r53 Nov 6, 2026

Package

gomod istio.io/istio (Go)

Affected versions

>= 1.31.0, < 1.31.4
>= 1.30.0, < 1.30.8

Patched versions

1.31.4
1.30.8

Description

Summary

An AuthorizationPolicy when condition on request.headers[:authority] (or request.headers[host]) is matched case-sensitively, so a request with a differently-cased host bypasses it.

Details

to.operation.hosts has been matched case-insensitively since CVE-2021-39155, and GHSA-w44g-8m76-8gc5 did the same for methods. A when condition with key: request.headers[:authority] still goes through the generic header matcher and compiles to a case-sensitive Envoy :authority matcher. Envoy routes hosts case-insensitively, so a request for ADMIN.example.com reaches the admin.example.com route but does not match a DENY rule on request.headers[:authority], or does match an ALLOW rule with notValues. request.headers[host] has the same issue, because Envoy maps the host header to :authority. HTTP/1.1 and HTTP/2 are both affected.

Patches

Fixes are available in 1.30.8 and 1.31.4

Workarounds

Use to.operation.hosts / notHosts instead of when conditions on request.headers[:authority] or request.headers[host].

Proof of concept

  1. Route admin.example.com through an ingress gateway to a backend.

  2. Apply on the gateway:

    apiVersion: security.istio.io/v1
    kind: AuthorizationPolicy
    metadata:
      name: deny-admin
      namespace: istio-system
    spec:
      selector:
        matchLabels:
          istio: ingressgateway
      action: DENY
      rules:
      - when:
        - key: request.headers[:authority]
          values: ["admin.example.com"]
  3. curl -H 'Host: admin.example.com' http://$GW/ returns 403; curl -H 'Host: ADMIN.example.com' http://$GW/ reaches the backend.

Impact

Authorization bypass. A client can reach a host that an AuthorizationPolicy is meant to deny by changing the case of the Host / :authority header. Only policies using when conditions on request.headers[:authority] or request.headers[host] are affected; to.operation.hosts is not.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVE ID

No known CVE

Weaknesses

Improper Handling of Case Sensitivity

The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. Learn more on MITRE.

Credits