GHSA-xp9c-82x8-7f67
HIGHGHSA-xp9c-82x8-7f67 is a high-severity (CVSS 7.7) CWE-915 vulnerability in @node-red/runtime. O3 Security confirms whether GHSA-xp9c-82x8-7f67 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in Node-Red
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@node-red/runtimenpmDescription
Impact
Node-RED 1.2.7 and earlier contains a Prototype Pollution vulnerability in the admin API. A badly formed request can modify the prototype of the default JavaScript Object with the potential to affect the default behaviour of the Node-RED runtime.
Patches
The vulnerability is patched in the 1.2.8 release.
Workarounds
A workaround is to ensure only authorised users are able to access the editor url.
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Acknowledgements
Thanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @node-red/runtime | all versions | 1.2.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @node-red/runtime. 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/runtime to 1.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xp9c-82x8-7f67 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-xp9c-82x8-7f67 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-xp9c-82x8-7f67. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xp9c-82x8-7f67 in your dependencies?
O3 detects GHSA-xp9c-82x8-7f67 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.