EUVD-2026-55804
GHSA-xm8c-hvjf-c5q9
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
High complexity because exploitation requires both non-default --format flags and a malicious package in scope; UI:R since the developer must actively invoke those flags; I:L only for terminal display manipulation.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
2DescriptionCVE.org
npm-check-updates through 23.0.2, fixed in commit b554b84, contains a terminal escape sequence injection vulnerability that allows an attacker to embed arbitrary terminal control characters in a dependency's package.json homepage or repository URL fields. When a developer runs ncu with the --format homepage or --format repo option, unfiltered escape sequences are written directly to the terminal, enabling malicious output manipulation or other terminal-dependent effects.
AnalysisAI
Terminal escape sequence injection in npm-check-updates through 23.0.2 enables a supply-chain attacker who controls a malicious npm package's metadata to embed arbitrary VT100/OSC control sequences in the homepage or repository URL fields of package.json. When developers run ncu --format homepage or --format repo, these unfiltered sequences are written directly to the terminal, allowing output overwriting via bare carriage returns, terminal title hijacking via OSC sequences, and other display manipulation on developer workstations or CI runners. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires all three of the following conditions: (1) the developer or CI pipeline explicitly invokes npm-check-updates with the `--format homepage` or `--format repo` flag - these are non-default options absent from a standard `ncu` run; (2) at least one dependency in the project's scope has attacker-controlled escape sequences embedded in its `homepage`, `repository`, `engines.node`, or peer dependency metadata fields in `package.json`; and (3) the installed npm-check-updates version is 23.0.2 or earlier. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 5.3 (Medium) is broadly appropriate but may overstate complexity: the provided vector AV:N/AC:L/AT:N/PR:N/UI:P reflects that attack complexity is assessed as low, though exploitation in practice requires a developer to explicitly invoke two non-default flags (`--format homepage` or `--format repo`) while also having a malicious package in their dependency tree - conditions that together reduce realistic exploitation probability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A threat actor publishes a malicious npm package to the public registry and embeds an OSC terminal escape sequence such as `\x1b]0;pwned\x07` in the `homepage` field of its `package.json`, or a bare carriage return (`\r`) in the `repository` field to overwrite a rendered URL with attacker-controlled text. When a developer auditing dependency updates runs `ncu --format homepage` on a project that lists this package as a dependency, npm-check-updates reads the metadata, interpolates it unfiltered into the terminal table, and the escape sequence executes in the developer's terminal - setting the window title to attacker-controlled text or making a malicious URL appear to display as a legitimate one. … |
| Remediation | Upgrade npm-check-updates to a version that includes commit b554b84848fc0b08a9d2b3d3db15e351387168cf; verify the installed version includes this commit by checking the package changelog or running `npm info npm-check-updates` to confirm the latest published version post-fix, as an exact patched release number is not confirmed in the available intelligence. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
Directory traversal vulnerability in lib/app/index.js in Geddy before 13.0.8 for Node.js allows remote attackers to read
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Eval injection vulnerability in index.js in the syntax-error package before 1.1.1 for Node.js 0.10.x, as used in IBM Rat
Same technique Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today