Apache APISIX mTLS routes reachable without a certificate (CVE-2026-124723)
With two URI settings enabled, APISIX 3.18.0 through 3.19.0 can send an uncertified client to a protected upstream.
Incorrect mTLS authorization in Apache APISIX with encoded slash matching
Apache APISIX can mis-authorize requests when match_uri_encoded_slash is enabled and skip_mtls_uri_regex is set. A remote client without a certificate can reach an upstream behind an mTLS-required route, but only for paths that decode to an exempted URI. This affects Apache APISIX 3.18.0 through 3.19.0.
What to do: Upgrade Apache APISIX to 3.20.0, which fixes the issue.
| Product | Affected | Fixed in |
|---|---|---|
| Apache APISIX | from 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.
Interpretation Conflict, leading to Incorrect Authorization vulnerability in Apache APISIX. With match_uri_encoded_slash enabled and skip_mtls_uri_regex configured, a client without a certificate can reach an upstream behind a route that requires one, limited to request paths that decode to an exempted URI. 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.
With two URI settings enabled, APISIX 3.18.0 through 3.19.0 can send an uncertified client to a protected upstream.
Today 2.5K readers · 2.8K views · 144 reads · all time 206K views