GHSA-j7cg-h9v9-6vqp is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in irrelon-path. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-j7cg-h9v9-6vqp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in irrelon-path and @irrelon/path
Real-World Exposure
irrelon-path📦@irrelon/pathReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
The package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | irrelon-path | all versions | 4.7.0 |
| 📦npm | @irrelon/path | all versions | 4.7.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for irrelon-path. 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 irrelon-path to 4.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7cg-h9v9-6vqp 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-j7cg-h9v9-6vqp 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-j7cg-h9v9-6vqp. 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-j7cg-h9v9-6vqp in your dependencies?
O3 detects GHSA-j7cg-h9v9-6vqp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.