← Back
CVE-2026-54753
medium
CVSS 5.9
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-749) exists in nx. Attackers reach the vulnerable code path via `GET /help` without authentication.
📍 Affected scope
nx — . Attack surface: GET /help / `help.command`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **23.0.0-beta.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt 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 があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade nx to 23.0.0-beta.2ステージング環境で 23.0.0-beta.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /help on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
nx
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"23.0.0-beta.2"}]}]
References
- web https://github.com/nrwl/nx/pull/35494
- web https://github.com/nrwl/nx/security/advisories/GHSA-g2r8-wvmj-jf5w
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54753
- web https://github.com/nrwl/nx/commit/7620c1ffe598086ce5e66457c7e6e38799bb499d
- web https://github.com/nrwl/nx/commit/e59122c5569cf201561b9995ce4e34a304f4fb03
- web https://github.com/nrwl/nx/releases/tag/22.7.2
- web https://github.com/advisories/GHSA-g2r8-wvmj-jf5w