GHSA-2xx4-jj5v-6mff is a high-severity (CVSS 7.5) Path Traversal vulnerability in github.com/projectdiscovery/nuclei/v2. A fix is available for github.com/projectdiscovery/nuclei/v2 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2xx4-jj5v-6mff.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.9go get github.com/projectdiscovery/nuclei/v2@v2.9.9 |
| 🐹Go | github.com/projectdiscovery/nuclei | all versions | 2.9.9go get github.com/projectdiscovery/nuclei@v2.9.9 |
Affected Products
nucleiprojectdiscoveryDetection & 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-2xx4-jj5v-6mff in your dependencies?
Find it across Go, including transitive dependencies.