<?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>Zoraxy (&lt;= 3.3.4) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/zoraxy--3.3.4/</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>Mon, 12 Oct 2026 18:32:04 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/zoraxy--3.3.4/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>Authorization Bypass in Zoraxy via Path Exception Matcher</title><link>https://feed.craftedsignal.io/briefs/2026-10-zoraxy-auth-bypass/</link><pubDate>Mon, 12 Oct 2026 18:32:04 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-zoraxy-auth-bypass/</guid><description>Zoraxy versions up to 3.3.4 are vulnerable to a remote authorization bypass in the Path Exception Matcher component that allows attackers to manipulate PathPrefix arguments.</description><content:encoded><![CDATA[<p>Zoraxy versions up to 3.3.4 contain a critical vulnerability in the <code>handleBasicAuth</code> function within <code>mod/dynamicproxy/authProviders.go</code>. The issue stems from the Path Exception Matcher component failing to properly validate the <code>PathPrefix</code> argument during authorization checks. By manipulating this argument, a remote, unauthenticated attacker can bypass existing authentication controls. The flaw is documented as CVE-2026-108899 and is reported to have public exploit code available, increasing the risk of exploitation by threat actors. Organizations utilizing Zoraxy as a reverse proxy or dynamic routing solution should prioritize patching, as successful exploitation results in unauthorized access to internal resources protected by the proxy.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows unauthorized access to backend services that rely on Zoraxy for Basic Authentication enforcement. This bypass can lead to the exposure of sensitive internal data, unauthorized administrative access, or facilitate further exploitation of protected backend applications. Given the nature of Zoraxy as a proxy, this flaw affects any network sector or infrastructure segment where the proxy is deployed as a gatekeeper.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade all instances of Zoraxy to version 3.3.5-rc1 or newer to remediate the vulnerability associated with CVE-2026-108899.</li>
<li>If an immediate upgrade is not feasible, apply the source code patch provided in commit 37cd0f27b17cd15cfa4af409bfec943146f5fdfe.</li>
<li>Review logs for unusual requests to endpoints typically protected by Basic Auth that deviate from standard organizational traffic patterns, specifically looking for anomalous <code>PathPrefix</code> parameters.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>