CVE Index中文
L3 · ShartedApache APISIX · API gateway · authentication · authorizationapache-apisix-gateway

Apache APISIX discloses seven gateway access-control vulnerabilities

Apache disclosed seven flaws fixed in APISIX 3.20.0, including a path normalization mismatch, spoofed identity headers and bypasses involving Keycloak, mTLS and MCP. Exposure depends on route, plugin and upstream configuration.

Disclosed
Nov 13, 2026
Public disclosure date
Severity
CVSS 7.8 × 1
7 CVEs tracked here
Splash zone
APISIX through 3.19.0 with affected route or plugin configurations. See each advisory for the starting version and prerequisites.
Apache APISIX · API gateway · authentication · authorization
In the wild
Unknown

What happened

The path normalization flaw can let a request match an unauthenticated route at the gateway and resolve to a protected path at the upstream. The route must share an upstream with the protected route, and the upstream must handle encoded dot segments as described in Apache’s advisory. Other bypasses depend on the corresponding plugins or TLS options. Apache’s advisories do not report exploitation in the wild. The impact on gateway access controls warrants L3.

What’s in the bowl

Authentication bypass through path normalization

From 0.9 through 3.19.0, an unauthenticated route can expose protected paths when both routes share an upstream that does not collapse encoded dot segments.

Forged identity on skipped or degraded authentication

From 3.18.0 through 3.19.0, tokenless jwe-decrypt requests can pass a caller-supplied value if strict is false and forward_header differs from the token header. A forward-auth request can do likewise if allow_degradation is enabled and the auth service is unavailable.

Wolf identity headers survive authentication fallback

From 3.8.0 through 3.19.0, multi-auth can retain caller-supplied Wolf identity headers when it falls back from wolf-rbac to another successful authenticator. This matters when the upstream trusts those headers.

Keycloak partial grant bypass

From 1.4.0 through 3.19.0, an authenticated caller with only part of the required grant can reach the upstream. This can include methods the authorization server denied.

Encoded path bypasses mutual TLS

From 3.18.0 through 3.19.0, enabling match_uri_encoded_slash with skip_mtls_uri_regex lets a client without a certificate reach a protected upstream when the request decodes to an exempt path.

MCP call reaches undeclared API path

In 3.19.0, an openapi-to-mcp caller can use a declared tool's HTTP method and the route's credentials to access an API path missing from the OpenAPI document.

MCP call overrides a configured identity

In 3.19.0, an openapi-to-mcp caller can spoof an upstream identity if the route adds an identity header that the document also declares.

Fixed versions

ProductSafe fromNote
Apache APISIX3.20.0First release fixing the seven advisories

Crime-scene timeline

  1. Nov 11, 2026

    Apache announces APISIX 3.20.0

    The release notes describe behavior changes and migration steps.

  2. Nov 13, 2026

    Apache publishes the seven security advisories

    The notices identify affected releases and specific configuration prerequisites.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.