CVE-2026-124723 · Infrastructure
NO FIX YET · SEE WHAT TO DO
With match_uri_encoded_slash enabled and skip_mtls_uri_regex set, a client without a certificate can reach an upstream behind a route that requires one. The request path must decode to an exempted URI, which bypasses the mutual TLS requirement.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only deployments running Apache APISIX 3.18.0 through 3.19.0 that enable match_uri_encoded_slash and configure skip_mtls_uri_regex on a route requiring client certificates. Deployments without both settings, or without mTLS routes, are not exposed.
Not affected if default-config, match-uri-encoded-slash-disabled, no-mtls-routes
Who cares apache-apisix, api-gateway, mtls, self-hosted
apisix version, affected range is 3.18.0 through 3.19.0match_uri_encoded_slash enabled and skip_mtls_uri_regex set in the APISIX configuration3.20.0Interpretation 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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.