CVE-2026-54753

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
52.6%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_pr, github.
github Patch Available

`nx graph` dev server permissive CORS policy · Advisory · nrwl/nx · GitHub

https://github.com/nrwl/nx/security/advisories/GHSA-g2r8-wvmj-jf5w
github_pr Patch Available

fix(core): remove access control header from graph app

Patch available: nrwl/nx 23.0.0-beta.12 (PR #35494 merged 2026-04-29)

https://github.com/nrwl/nx/pull/35494

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 23:48 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 21:53 UTCEG score recompute
  5. 2026-07-09 19:58 UTCEG score recompute
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 18:03 UTCEG score recompute
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-07 16:08 UTCEG score recompute
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 13:06 UTCEG score recompute
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 11:01 UTCEG score recompute
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 09:06 UTCEG score recompute
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 07:11 UTCEG score recompute
Show 14 more
  1. 2026-07-02 05:16 UTCEG score recompute
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 03:22 UTCEG score recompute
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 01:27 UTCEG score recompute
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 23:32 UTCEG score recompute
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-27 21:37 UTCEG score recompute
  13. 2026-06-26 19:42 UTCEG score recompute
  14. 2026-06-26 19:41 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-54753?
CVE-2026-54753 is a medium vulnerability published on June 26, 2026. 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…
When was CVE-2026-54753 disclosed?
CVE-2026-54753 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54753 actively exploited?
CVE-2026-54753 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54753?
CVE-2026-54753 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-54753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54753, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54753

Explore →

Is Your Infrastructure Affected by CVE-2026-54753?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs