Is CVE-2026-94269 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-94269 being exploited in the wild.

How severe is CVE-2026-94269?

Informational severity, published 1 October 2026.

Which products and versions are affected?

Apache APISIX 2.14.1 through 3.18.0.

Is there a fix for CVE-2026-94269?

Yes: fixed in 3.19.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-94269 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-94269?

Check whether you run Apache APISIX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-94269: Apache APISIX authorization bypass via non-canonical URL paths

CVE-2026-94269 · Severity: info · Published 2026-10-01

Apache APISIX is an API gateway that protects upstream services using route-based policies and authentication. In certain configurations, attackers can bypass these protections by crafting specially encoded URL paths, gaining unauthorized access to protected endpoints that should have been rejected.

Technologies: Apache APISIX. Vendors: Apache.

Quick answers

Is CVE-2026-94269 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-94269 being exploited in the wild.
How severe is CVE-2026-94269?: Informational severity, published 1 October 2026.
Which products and versions are affected?: Apache APISIX 2.14.1 through 3.18.0.
Is there a fix for CVE-2026-94269?: Yes: fixed in 3.19.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94269 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-94269?: Check whether you run Apache APISIX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.19.0

Technical details

A non-canonical URL path normalization vulnerability allows attackers to reach upstream endpoints without matching the intended route's authorization policies. When a permissive route overlaps a protected one, servlet-style path normalization can cause a request to be routed incorrectly, skipping policy enforcement. The vulnerability affects versions 2.14.1 through 3.18.0 and requires network access with minimal preconditions.

Affected products

Apache APISIX 2.14.1 through 3.18.0

Timeline

2026-10-01: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.