<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Apache APISIX - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/apache-apisix/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 13 Nov 2026 23:24:54 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/apache-apisix/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Apache APISIX: Authentication bypass via client-supplied header preservation (CVE-2026-124666)</title><link>https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-header-spoofing-cve-2026-124666/</link><pubDate>Fri, 13 Nov 2026 23:24:54 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-header-spoofing-cve-2026-124666/</guid><description>Apache APISIX versions 3.8.0 through 3.19.0 contain an authentication bypass vulnerability where client-supplied Wolf identity headers are preserved during multi-authentication fallback, allowing identity spoofing in downstream services.</description><content:encoded><![CDATA[<p>Apache APISIX versions 3.8.0 through 3.19.0 are vulnerable to an authentication bypass via spoofing. 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 headers may be impacted.</p>
<h2 id="impact">Impact</h2>
<p>Client-supplied Wolf identity headers may remain in the request and be consumed by downstream services, potentially resulting in authentication bypass or identity spoofing.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Evaluate whether downstream services trust identity headers originated from the APISIX gateway.</p>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category></item><item><title>Apache APISIX: Authentication bypass via header spoofing (CVE-2026-124679)</title><link>https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-auth-bypass-cve-2026-124679/</link><pubDate>Fri, 13 Nov 2026 23:24:35 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-auth-bypass-cve-2026-124679/</guid><description>Apache APISIX versions 3.18.0 through 3.19.0 contain an authentication bypass vulnerability where unauthenticated clients can spoof identity headers when using the jwe-decrypt plugin with specific non-strict configurations.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache APISIX versions 3.18.0 through 3.19.0 are vulnerable to an authentication bypass via header spoofing (CVE-2026-124679). The issue occurs in routes configured with the <code>jwe-decrypt</code> plugin where <code>strict</code> is set to <code>false</code> and a <code>forward_header</code> is defined that differs from the token header. Under these conditions, an unauthenticated client can supply a malicious identity header directly, which the upstream service subsequently processes as trusted, decrypted plaintext.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an unauthenticated attacker to spoof their identity, effectively bypassing authentication controls and gaining unauthorized access to services protected by the affected APISIX gateway configuration.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Inventory all APISIX instances using the <code>jwe-decrypt</code> plugin. Ensure that any routes using this plugin are configured with <code>strict: true</code> or verify that the <code>forward_header</code> and token header configurations do not allow arbitrary header injection from client requests. Monitor upstream service logs for authentication anomalies or unexpected identity values until patches can be applied.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache APISIX: Route-level authentication bypass (CVE-2026-124680)</title><link>https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-auth-bypass-cve-2026-124680/</link><pubDate>Fri, 13 Nov 2026 23:24:14 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-auth-bypass-cve-2026-124680/</guid><description>Apache APISIX versions 0.9 through 3.19.0 contain an authentication bypass vulnerability due to path normalization mismatches between the routing layer and upstream forwarding.</description><content:encoded><![CDATA[<p>Apache APISIX versions 0.9 through 3.19.0 are affected by an interpretation conflict (CVE-2026-124680) resulting in an authentication bypass vulnerability. When a route without authentication is present on the same upstream as a route protected by an authentication plugin, an unauthenticated client can access the protected upstream path due to a path normalization mismatch.</p>
<h2 id="impact">Impact</h2>
<p>Unauthenticated attackers can reach upstream paths intended to be protected by route-level authentication plugins.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-124680</category><category>vulnerability</category><category>api-gateway</category></item><item><title>Apache APISIX: mTLS bypass via interpretation conflict (CVE-2026-124723)</title><link>https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-mtls-bypass-cve-2026-124723/</link><pubDate>Fri, 13 Nov 2026 23:23:44 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-apache-apisix-mtls-bypass-cve-2026-124723/</guid><description>Apache APISIX versions 3.18.0 through 3.19.0 contain an interpretation conflict that allows unauthenticated clients to bypass mTLS requirements when specific configuration options are enabled.</description><content:encoded><![CDATA[<p>Apache APISIX versions 3.18.0 through 3.19.0 are affected by an interpretation conflict (CVE-2026-124723) leading to incorrect authorization. The vulnerability occurs when 'match_uri_encoded_slash' is enabled alongside a configured 'skip_mtls_uri_regex'. This specific combination allows clients to access upstream resources protected by mutual TLS without providing a valid certificate. The vulnerability is assigned a CVSS 4.0 score of 6.3 (AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N).</p>
<h2 id="impact">Impact</h2>
<p>Unauthorized access to backend upstream resources that are intended to be restricted by mTLS. This could potentially expose sensitive internal services or APIs to unauthenticated external actors depending on the specific route configuration.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Upgrade Apache APISIX to a non-vulnerable version immediately. Organizations utilizing the affected configurations (enabling both 'match_uri_encoded_slash' and 'skip_mtls_uri_regex') should audit their route configurations to ensure that security controls are functioning as intended until an upgrade can be performed.</p>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category></item></channel></rss>