<?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>Cpe:2.3:a:apache:apisix:3.19.0:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3aapacheapisix3.19.0/</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:35 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3aapacheapisix3.19.0/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 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></channel></rss>