<?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/"><channel><title>Network-AI (Npm: Network-Ai) (Versions 5.12.2 Through 5.13.3) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/network-ai-npm-network-ai-versions-5.12.2-through-5.13.3/</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, 20 Jul 2026 12:31:09 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/network-ai-npm-network-ai-versions-5.12.2-through-5.13.3/feed.xml" rel="self" type="application/rss+xml"/><item><title>Authorization Bypass in Network-AI npm Package CVE-2026-64622</title><link>https://feed.craftedsignal.io/briefs/2026-07-network-ai-auth-bypass/</link><pubDate>Mon, 20 Jul 2026 12:31:09 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-network-ai-auth-bypass/</guid><description>Network-AI (npm: network-ai) versions 5.12.2 through 5.13.3 are vulnerable to an authorization bypass (CVE-2026-64622) that allows unauthenticated actors to access sensitive approval request details via specific GET read routes like /approvals/. This vulnerability discloses critical information such as shell-command strings, file paths, justifications, and risk levels. Additionally, a hardcoded 'Access-Control-Allow-Origin: *' header in responses facilitates cross-origin data disclosure, enabling potential exfiltration from malicious websites an operator might visit.</description><content:encoded><![CDATA[<p>CVE-2026-64622 impacts <code>network-ai</code> npm package versions 5.12.2 through 5.13.3, allowing unauthenticated actors to bypass authorization checks on specific GET read routes related to the <code>ApprovalInbox</code>. This flaw means that even when a secret is configured, sensitive approval request details become accessible without authentication. The affected routes, including <code>/approvals/?status=all</code>, <code>/approvals/:id</code>, <code>/approvals/stats</code>, and <code>/approvals/sse</code>, disclose full <code>ApprovalEntry</code> content such as action/target shell-command strings, file paths, justifications, and risk levels. Compounding the issue, all responses from these routes carry a hardcoded <code>Access-Control-Allow-Origin: *</code> header, which facilitates cross-origin data disclosure. This allows malicious websites, if visited by an operator, to potentially exfiltrate the exposed sensitive data. This vulnerability represents an incomplete fix for a previously identified issue (GHSA-mxjx-28vx-xjjj).</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a <code>network-ai</code> instance running vulnerable versions 5.12.2 through 5.13.3.</li>
<li>The attacker sends an unauthenticated HTTP GET request to one of the vulnerable <code>ApprovalInbox</code> read routes, such as <code>/approvals/?status=all</code>, <code>/approvals/:id</code>, <code>/approvals/stats</code>, or <code>/approvals/sse</code>.</li>
<li>Due to the CVE-2026-64622 authorization bypass, the <code>network-ai</code> application fails to apply the configured <code>checkAuth/secret</code>.</li>
<li>The application responds with full <code>ApprovalEntry</code> content, which includes sensitive data like shell-command strings, file paths, justifications, and risk levels, without requiring authentication.</li>
<li>The response also contains a hardcoded <code>Access-Control-Allow-Origin: *</code> header, making the disclosed data vulnerable to cross-origin access.</li>
<li>If an operator of the <code>network-ai</code> application visits a malicious website, that website can initiate cross-origin requests to the vulnerable <code>network-ai</code> instance.</li>
<li>The malicious website successfully retrieves the sensitive approval data and exfiltrates it to an attacker-controlled server.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-64622 leads to unauthorized disclosure of highly sensitive information, including critical operational details like shell-command strings, internal file paths, and business justifications for approvals. This exposure can provide attackers with valuable intelligence for further attacks, potentially leading to privilege escalation, system compromise, or data manipulation. The hardcoded <code>Access-Control-Allow-Origin: *</code> header also enables severe privacy and data exfiltration risks, as any visited malicious website could programmatically extract this sensitive data, impacting organizations using the vulnerable versions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch CVE-2026-64622 by immediately updating the <code>network-ai</code> npm package to a version outside the affected range (i.e., higher than 5.13.3 or lower than 5.12.2 if applicable).</li>
<li>Deploy the Sigma rule &quot;Detect CVE-2026-64622 Exploitation Attempts on Network-AI&quot; to your SIEM solution to alert on suspicious access patterns.</li>
<li>Monitor web server access logs for unauthenticated GET requests to the <code>/approvals/?status=all</code>, <code>/approvals/:id</code>, <code>/approvals/stats</code>, and <code>/approvals/sse</code> endpoints, referencing the log source category <code>webserver</code>.</li>
<li>Implement Web Application Firewall (WAF) rules to restrict or block unauthenticated access to the <code>network-ai</code> <code>/approvals/*</code> paths mentioned in the attack chain, if not required for legitimate operations.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>authorization-bypass</category><category>information-disclosure</category><category>npm</category></item></channel></rss>