<?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>Nango - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/nango/</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, 04 Sep 2026 19:26:55 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/nango/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>Authentication Bypass in Nango Runner tRPC Server</title><link>https://feed.craftedsignal.io/briefs/2026-09-nango-auth-bypass/</link><pubDate>Fri, 04 Sep 2026 19:26:55 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-nango-auth-bypass/</guid><description>Nango versions prior to 0.71.6 contain an authentication bypass vulnerability allowing unauthenticated attackers to achieve remote code execution via the tRPC runner server.</description><content:encoded><![CDATA[<p>Nango versions prior to 0.71.6 are vulnerable to an authentication bypass in the runner tRPC server. An unauthenticated attacker with network access to the runner service can invoke the exposed 'start' procedure without providing the required RUNNER_SECRET_KEY. This flaw allows the execution of arbitrary JavaScript code within the context of the runner process, leading to remote code execution (RCE). The vulnerability stems from a failure to enforce authentication controls on specific internal tRPC procedures, making it a critical risk for deployments where the runner is reachable by untrusted network entities. Defenders must upgrade to version 0.71.6 or later to enforce proper credential validation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker performs network reconnaissance to identify reachable runner ports associated with Nango deployments.</li>
<li>Attacker establishes a network connection to the target tRPC runner server port.</li>
<li>Attacker crafts a malicious tRPC request targeting the 'start' procedure.</li>
<li>Attacker omits or provides an invalid RUNNER_SECRET_KEY in the request payload.</li>
<li>The Nango runner server fails to validate the request, incorrectly assuming authorization.</li>
<li>The 'start' procedure processes the request and executes the embedded malicious JavaScript code.</li>
<li>Attacker achieves remote code execution within the runner process context.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to execute arbitrary JavaScript code on the Nango runner service. This can lead to full system compromise, unauthorized data access, and potential lateral movement within the network infrastructure where the runner is hosted.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Upgrade Nango to version 0.71.6 or later immediately to patch CVE-2026-9317.</li>
<li>Restrict network access to the Nango runner tRPC server port to authorized management subnets only.</li>
<li>Implement egress filtering and monitoring to detect suspicious network activity originating from the Nango runner process.</li>
</ol>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>remote-code-execution</category><category>nango</category></item></channel></rss>