Vulnerability in nx (CVE-2026-54753)
Summary
Vulnerability in nx (CVE-2026-54753). Confidential information can be exposed externally. Exploitable via GET /help. Mitigation: upgrade to 23.0.0-beta.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54753 has been found in nx.
Attackers can target a specific entry point like GET /help over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade nx to 23.0.0-beta.2 or later.
If unsure, ask your IT team or search "nx CVE-2026-54753" on the vendor's site.
CVE-2026-54753 (nx) — CWE-749 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /help / help.command
Patched: 23.0.0-beta.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-749) exists in nx. Attackers reach the vulnerable code path via GET /help without authentication.
Check the vendor advisory for the affected versions of nx. Attack surface: GET /help / help.command.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 23.0.0-beta.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /help requests with malformed payloads or SQL meta-characters. Run grep -r 'nx' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nxを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /help' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /helpへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade nx to 23.0.0-beta.2ステージング環境で 23.0.0-beta.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /help on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com