VulnerabilityPublished 13 Aug 2026Updated 29 Oct 2026

CVE-2026-54753: `nx graph` dev server permissive CORS policy

Affects nxSource GCVE Database

Compare

Authoritative record:CVE-2026-54753· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 22.7.2 when convenient.

Data as of 30 Oct 2026, 08:15 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 22.7.2

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nx to 22.7.2.

Affected software

Product	Affected	Fixed in
Homebrewnx`pkg:brew/nx`Other threats	Affected >=21.0.4 <22.7.2	Fixed in 22.7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in `nx` version 22.7.2 and later (including 23.0.0 and above). Users should upgrade to these versions to eliminate the permissive CORS header and prevent cross-origin data leaks. The 21.x line is unpatched and should be upgraded. No additional mitigation is required beyond applying the official fix.

Description

The `nx graph` development server had a permissive CORS policy that allowed any website to read responses from the local server, including sensitive project graph data and the output of a `/help` endpoint that executes configured help commands. This could lead to cross-origin information disclosure. Exploitation requires the developer to be running the vulnerable `nx graph` server and to visit a malicious website. Arbitrary command execution is only possible if a malicious help command is already configured in the workspace, which requires prior compromise. The issue affects versions from 17.0.4 up to but not including 22.7.2 and certain beta versions before 23.0.0-beta.2. A fix is available starting with version 22.7.2.

Impact

This vulnerability allows cross-origin information disclosure from the local `nx graph` server, exposing project metadata and potentially sensitive command output to any website the developer visits. Although arbitrary command execution via the `/help` endpoint is theoretically possible, it requires a malicious help command to already exist in the workspace, which implies prior compromise. The overall impact is medium severity due to the requirement for user interaction and limited execution risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 08:15 UTC

Technical details

References

Community reviews

Related threats