GHSA-2xx4-jj5v-6mff
HIGHNuclei Path Traversal vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/projectdiscovery/nuclei/v2🐹github.com/projectdiscovery/nucleiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Overview
We have identified and addressed a security issue in the Nuclei project that affected users utilizing Nuclei as Go code (SDK) running custom templates. This issue did not affect CLI users. The problem was related to sanitization issues with payloads loading in sandbox mode.
Details
In the previous versions, there was a potential risk with payloads loading in sandbox mode. The issue occurred due to relative paths not being converted to absolute paths before doing the check for sandbox flag allowing arbitrary files to be read on the filesystem in certain cases when using Nuclei from Go SDK implementation.
This issue has been fixed in the latest release, v2.9.9. We have also enabled sandbox by default for filesystem loading. This can be optionally disabled if required.
The -sandbox option has been deprecated and is now divided into two new options: -lfa (allow local file access) which is disabled by default and -lna (restrict local network access) which can be optionally disabled by user. The -lfa allows file (payload) access anywhere on the system (disabling sandbox effectively), and -lna blocks connections to the local/private network.
Affected Versions
This issue affected all versions of Nuclei prior to v2.9.9.
Patches
We recommend all users upgrade to the latest version, v2.9.9, which includes the security fix.
References
Acknowledgments
We would like to thank keomutchoiboi who reported this issue to us via our security email, [email protected]. We appreciate the responsible disclosure of this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/projectdiscovery/nuclei/v2 | all versions | 2.9.9 |
| 🐹Go | github.com/projectdiscovery/nuclei | all versions | 2.9.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/projectdiscovery/nuclei/v2. 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 github.com/projectdiscovery/nuclei/v2 to 2.9.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xx4-jj5v-6mff 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-2xx4-jj5v-6mff 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-2xx4-jj5v-6mff. 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-2xx4-jj5v-6mff in your dependencies?
O3 detects GHSA-2xx4-jj5v-6mff across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.