<?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>QuickJS - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/quickjs/</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>Wed, 02 Sep 2026 17:16:10 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/quickjs/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>Out-of-Bounds Write in NGINX JavaScript (njs) XML Module</title><link>https://feed.craftedsignal.io/briefs/2026-09-nginx-njs-xml-vuln/</link><pubDate>Wed, 02 Sep 2026 17:16:10 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-nginx-njs-xml-vuln/</guid><description>CVE-2026-78689 allows remote unauthenticated attackers to trigger an out-of-bounds heap write in the NGINX JavaScript (njs) and QuickJS (qjs) XML module via crafted namespace prefix lists.</description><content:encoded><![CDATA[<p>CVE-2026-78689 is an out-of-bounds heap write vulnerability affecting the XML module of the NGINX JavaScript (njs) engine and the QuickJS (qjs) engine. The flaw is located in the xml.exclusiveC14n() method, which fails to safely process an XML namespace prefix list provided by an external source. An unauthenticated remote attacker can exploit this by passing a crafted prefix list to the method.</p>
<p>When using the njs engine, the out-of-bounds write corrupts adjacent heap objects, leading to an immediate crash of the NGINX worker process. When using the QuickJS engine, the vulnerability causes memory leakage on every request, resulting in memory exhaustion. The nginx-saml reference implementation is specifically vulnerable during SAML signature verification, as it processes the InclusiveNamespaces/@PrefixList from untrusted SAML messages before verifying the digital signature. Consequently, attackers can trigger the crash or memory growth using crafted SAML Response, Assertion, LogoutRequest, or LogoutResponse packets. While remote code execution has not been observed, it remains a theoretical possibility depending on specific platform memory layout.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability impacts the availability of NGINX instances processing XML or SAML data. Successful exploitation leads to denial of service through repeatable worker process restarts (njs engine) or rapid worker memory growth (QuickJS engine). Because the flaw triggers before SAML signature validation, attackers do not require valid credentials or legitimate SAML tokens to impact the target service.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Identify all instances using the <code>nginx-saml</code> reference implementation and upgrade to the patched version once available.</li>
<li>Review NGINX configurations for usages of <code>xml.exclusiveC14n()</code> that process untrusted XML input and implement rigorous input validation for the <code>PrefixList</code> attribute.</li>
<li>Monitor NGINX error logs for recurring &quot;worker process exited with signal&quot; events, which may indicate crash-based denial of service attempts.</li>
<li>Monitor memory usage of NGINX worker processes to detect memory exhaustion patterns indicative of QuickJS exploitation.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>denial-of-service</category><category>cve-2026-78689</category></item><item><title>Authentication Bypass in NGINX JavaScript and QuickJS Engines</title><link>https://feed.craftedsignal.io/briefs/2026-09-nginx-auth-bypass/</link><pubDate>Wed, 02 Sep 2026 17:15:05 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-nginx-auth-bypass/</guid><description>An authentication bypass flaw in NGINX JavaScript (njs) and QuickJS (qjs) engines allows unauthenticated attackers to trigger a fail-open state in access control logic, potentially granting unauthorized access to protected resources.</description><content:encoded><![CDATA[<p>The NGINX JavaScript (njs) and QuickJS (qjs) engines contain a vulnerability involving the js_access handler during asynchronous request body processing. When an exception occurs during the asynchronous access-control evaluation phase - specifically before the handler can return an explicit access denial - the engine may fail open. This misconfiguration in the access validation logic permits the request to proceed to downstream resources despite failing security checks.</p>
<p>An unauthenticated remote attacker can exploit this condition by sending a crafted HTTP request designed to trigger an error within the access-control JavaScript logic. This results in an authorization bypass, potentially allowing access to protected endpoints that should have been restricted. This vulnerability exists within the data plane, impacting any application relying on the njs or qjs access control handlers for security enforcement.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated remote attackers to bypass security controls defined within the js_access handler. This can result in unauthorized access to sensitive application data or protected administrative functions. As this is a data plane issue affecting request processing, it does not involve exposure of the server control plane but directly undermines the security posture of the web application.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Identify all instances of NGINX utilizing the <code>js_access</code> handler for security controls.</li>
<li>Audit JavaScript access control logic to ensure that error conditions do not result in a default-allow state.</li>
<li>Monitor web server error logs for unexpected exceptions occurring within JavaScript access handlers, which may indicate exploitation attempts.</li>
<li>Apply patches provided by the software vendor once available for NGINX and affected distributions.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>