How severe is GHSA-2hw7-mxvj-m455?

No CVSS score has been assigned to GHSA-2hw7-mxvj-m455 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2hw7-mxvj-m455?

GHSA-2hw7-mxvj-m455 affects the following packages: node-red-dashboard (npm). Ecosystems affected: npm.

How do I fix GHSA-2hw7-mxvj-m455?

Update node-red-dashboard to 2.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hw7-mxvj-m455 is resolved across your whole dependency graph.

How do I detect GHSA-2hw7-mxvj-m455 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-red-dashboard. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2hw7-mxvj-m455 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2hw7-mxvj-m455?

O3 pinpoints whether GHSA-2hw7-mxvj-m455 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2hw7-mxvj-m455 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2hw7-mxvj-m455 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-2hw7-mxvj-m455?

GHSA-2hw7-mxvj-m455 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-2hw7-mxvj-m455?

A Nuclei detection template exists for GHSA-2hw7-mxvj-m455, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-2hw7-mxvj-m455 published, and has it been updated?

GHSA-2hw7-mxvj-m455 was published on January 29, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-2hw7-mxvj-m455

Fix: node-red/node-red-dashboard@f48f356

GHSA-2hw7-mxvj-m455 is a Path Traversal vulnerability in node-red-dashboard. O3 Security confirms whether GHSA-2hw7-mxvj-m455 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Path traversal in Node-RED-Dashboard

Also known asCVE-2021-3223

Published

Jan 29, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

node-red-dashboardnpm

42Kdownloads / week

Description

In Node-RED-Dashboard before 2.26.2 there is a path traversal vulnerability. It allows ui_base/js/..%2f directory traversal to read files.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-red-dashboard`	all versions	2.26.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-red-dashboard. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update node-red-dashboard to 2.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hw7-mxvj-m455 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2hw7-mxvj-m455 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2hw7-mxvj-m455. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Node-RED-Dashboard before 2.26.2 there is a path traversal vulnerability. It allows ui_base/js/..%2f directory traversal to read files.

O3 Security · Impact-Aware SCA

Is GHSA-2hw7-mxvj-m455 in your dependencies?

O3 detects GHSA-2hw7-mxvj-m455 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works