Is github.com/projectdiscovery/nuclei 2.9 vulnerable?
Go · 11 releases from 2.9.0 to 2.9.15 · latest github.com/projectdiscovery/nuclei is 1.1.7 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. github.com/projectdiscovery/nuclei 2.9.15, the last 2.9 release, is affected by 10 known security advisories (10 low), including CVE-2026-76802, CVE-2026-76805, CVE-2026-76804. 1 more affects earlier 2.9.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/projectdiscovery/nuclei?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/projectdiscovery/nuclei 2.9.15
Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei: Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei: Local File Read via Workflow File-Protocol Gate Bypass in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei: Local File Read via MySQL Client Sandbox Bypass in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei: Environment variable disclosure via Response-Derived DSL Expressions in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei: Local File Read via require() Module Loader Bypass in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei Template Signature Verification Bypass in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
projectdiscovery/nuclei allows unsigned code template execution through workflows in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Nuclei allows unsigned code template execution through workflows in github.com/projectdiscovery/nuclei
- Affected
- All versions
- Fixed in
- No fix released
Fixed within 2.9.x, affecting earlier releases
Nuclei Path Traversal vulnerability
- Affected
- <2.9.9
- Fixed in
- 2.9.9
Every github.com/projectdiscovery/nuclei 2.9.x release
Affected: 2.9.0 to 2.9.15. Latest github.com/projectdiscovery/nuclei: 1.1.7.
| Version | Known advisories |
|---|---|
| github.com/projectdiscovery/nuclei 2.9.15 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920 |
| github.com/projectdiscovery/nuclei 2.9.10 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920 |
| github.com/projectdiscovery/nuclei 2.9.8 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.7 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.6 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.5 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.4 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.3 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.2 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.1 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
| github.com/projectdiscovery/nuclei 2.9.0 | CVE-2026-76802, CVE-2026-76805, CVE-2026-76804, CVE-2026-76819, CVE-2026-76803, CVE-2026-41282, CVE-2026-41646, CVE-2024-43405, CVE-2024-40641, CVE-2024-27920, CVE-2023-37896 |
Which of your client projects are still on github.com/projectdiscovery/nuclei 2.9?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/projectdiscovery/nuclei version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/projectdiscovery/nuclei versions
- github.com/projectdiscovery/nuclei 2.8
- github.com/projectdiscovery/nuclei 2.7
- github.com/projectdiscovery/nuclei 2.6
- github.com/projectdiscovery/nuclei 2.5
- github.com/projectdiscovery/nuclei 2.4
- github.com/projectdiscovery/nuclei 1.1
- github.com/projectdiscovery/nuclei 1.0
- All github.com/projectdiscovery/nuclei advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.