Apache APISIX jwe-decrypt can pass spoofed identity (CVE-2026-124679)
On affected routes, an unauthenticated client can supply the header an upstream treats as gateway-decrypted plaintext.
Authentication bypass by spoofing in Apache APISIX
Apache APISIX can treat attacker-supplied values as gateway-decrypted plaintext. An unauthenticated network client can trigger this on routes using jwe-decrypt with strict set to false and a forward_header distinct from the token header, or when forward-auth has allow_degradation true and the auth service is unavailable. The attacker gains the upstream trust normally reserved for gateway-decrypted content. Versions 3.18.0 through 3.19.0 are affected.
What to do: Upgrade Apache APISIX to 3.20.0, which fixes CVE-2026-124679.
| Product | Affected | Fixed in |
|---|---|---|
| Apache APISIX | 3.18.0 through 3.19.0 | 3.20.0 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Authentication bypass by spoofing vulnerability in Apache APISIX. On routes using jwe-decrypt with strict: false and a forward_header distinct from the token header an unauthenticated client can supply the value the upstream treats as gateway-decrypted plaintext. Similar can happen when forward-auth is configured with allow_degradation: true, and the auth service is unavailable. This issue affects Apache APISIX: from 3.18.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.
On affected routes, an unauthenticated client can supply the header an upstream treats as gateway-decrypted plaintext.
Shiro through 3.0.0 is critical only with LDAP caching on; APISIX 3.18.0–3.19.0 is fixed in 3.20.0.
Today 2.5K readers · 2.8K views · 144 reads · all time 206K views