<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T02:44:07.143690+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-nx-cve-2026-54753</id>
    <title>BREW-nx-CVE-2026-54753 — `nx graph` dev server permissive CORS policy</title>
    <updated>2026-10-06T02:44:07.175030+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: nx</p>
<p>## Summary</p>
<p>The local HTTP server started by `nx graph` sent `Access-Control-Allow-Origin: *` on every response, letting any website a developer visited read the server's responses cross-origin — including the full project graph and the output of the `/help` endpoint, which runs a target's configured help command. The practical impact is typically **cross-origin information disclosure**, but can be arbitrary command injection in rare cases.</p>
<p>## Severity</p>
<p>Exploitation requires the developer to be running `nx graph` and to visit an attacker page. Any execution beyond benign help commands also requires a malicious target to already be present in the workspace (see Details).</p>
<p>## Affected &amp; Patched Versions</p>
<p>Package: `nx` (npm).</p>
<p>- **Affected:** `&gt;= 17.0.4, &lt; 22.7.2` and `&gt;= 23.0.0-beta.0, &lt; 23.0.0-beta.2`
- **Patched:** `22.7.2`+ (backport) and `23.0.0` (first in `23.0.0-beta.2`)</p>
<p>The wildcard CORS header was introduced in `17.0.4`; the `/help` execution endpoint in `19.4.0`. **The `21.x` line is not patched** — `21.x` users should upgrade to `22.7.2` or later.</p>
<p>## Details</p>
<p>`nx graph` starts a local server (default `http://127.0.0.1:4211`). Before the fix, its request handler set a wildcard CORS header on every response:</p>
<p>```ts
res.setHeader('Access-Control-Allow-Origin', '*');
```</p>
<p>The `/help` endpoint runs a target's configured command:</p>
<p>```ts
const command = target.metadata?.help?.command;
return execSync(command, { cwd: target.options?.cwd ?? workspaceRoot }).toString();
``…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-nx-cve-2026-54753"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-54753</id>
    <title>CVE-2026-54753 — Nx: `nx graph` dev server permissive CORS policy</title>
    <updated>2026-10-06T02:44:07.175188+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> nrwl nx</p>
<p>Nx is a monorepo solution for TypeScript and polyglot codebases. From 17.0.4 until 22.7.2 and 23.0.0-beta.2, the local HTTP server started by nx graph sent Access-Control-Allow-Origin: * on every response, letting any website a developer visited read the server's responses cross-origin — including the full project graph and the output of the /help endpoint, which runs a target's configured help command. The practical impact is typically cross-origin information disclosure, but can be arbitrary command injection in rare cases. This vulnerability is fixed in 22.7.2 and 23.0.0-beta.2.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-54753"/>
  </entry>
</feed>
