Search
Search Results (7 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-124726 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| Relative Path Traversal, with Unintended Proxy vulnerability in Apache APISIX. A caller of the MCP endpoint can invoke endpoints the OpenAPI document never declared, under the declared tool's HTTP method, using the credentials the Route adds. This issue affects Apache APISIX: from 3.19.0 before 3.20.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue. | ||||
| CVE-2026-124723 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| 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. | ||||
| CVE-2026-124719 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| Authentication bypass by spoofing vulnerability in Apache APISIX. When a Route's configured headers carry a caller identity and the OpenAPI document declares the same header, a caller can act as another identity against the upstream API. This issue affects Apache APISIX: from 3.19.0 before 3.20.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue. | ||||
| CVE-2026-124716 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| Incorrect Authorization vulnerability in Apache APISIX. An authenticated user who holds any one of a route's required permissions or scopes can reach the protected upstream without the others, including HTTP methods the authorization server denied. This issue affects Apache APISIX: from 1.4.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue. | ||||
| CVE-2026-124680 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| Interpretation Conflict, resulting in (Incorrect Authorization) vulnerability in Apache APISIX. An unauthenticated client can reach upstream paths protected by a route-level auth plugin when a route without auth exists on the same upstream and the upstream does not collapse encoded dot segments. This issue affects Apache APISIX: from 0.9 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue. | ||||
| CVE-2026-124679 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| 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. | ||||
| CVE-2026-124666 | 2 Apache, Apache Software Foundation | 3 Apache Apisix, Apisix, Apache Apisix | 2026-11-13 | N/A |
| Authentication bypass by spoofing vulnerability in Apache APISIX. On a route where multi-auth falls back from wolf-rbac to another successful authenticator, client-supplied Wolf identity headers can remain in the request. A downstream service that relies on those documented headers may therefore receive an identity that was not established by the successful authenticator. This issue affects Apache APISIX: from 3.8.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue. | ||||
Page 1 of 1.