Nuclei is a vulnerability scanner built on a simple YAML-based DSL. From 3.0.0 until 3.10.0, the DAST template loading branch does not apply the unsigned code-template signature check before accepting a template that contains both a fuzzing: block and an unsigned code: block. When an operator enables -dast, an untrusted multiprotocol template can place an unsigned code request into the execution queue and run arbitrary shell commands even without -code or a valid cryptographic signature. The issue affects CLI DAST scans and SDK integrations that enable DAST while accepting attacker-supplied templates. This issue is fixed in version 3.10.0.
CVE-2026-76802
MEDIUMPre-NVD 4.74.7—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(medium)
- EG Risk
- 21(Track)EG Risk 21/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity47% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 22, 2026Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
v3.10.0
Patch available: projectdiscovery/nuclei v3.10.0
https://github.com/projectdiscovery/nuclei/releases/tag/v3.10.0github_commit
commit 1c440e755a97 (projectdiscovery/nuclei)
Fix landed in projectdiscovery/nuclei commit 1c440e755a97 — awaiting tagged release
https://github.com/projectdiscovery/nuclei/commit/1c440e755a97471c56fb0276ee8a8c4132974645github_pr
check code template signature before dast load
Fix merged in projectdiscovery/nuclei PR #7472 on 2026-06-19 — awaiting tagged release
https://github.com/projectdiscovery/nuclei/pull/7472github Patch Available
Arbitrary Command Execution via DAST Code Signature Bypass · Advisory · projectdiscovery/nuclei · GitHub
https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jpf4-98qj-qr67Vendor Advisories for CVE-2026-76802(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/projectdiscovery/nuclei/v3 | — | 3.10.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 21:23 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 13:44 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 17:35 UTCEG score recompute
- 2026-09-22 17:10 UTCEG score recompute
- 2026-09-22 16:58 UTCEG score recompute
- 2026-09-22 16:54 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
9 shownGo:github.com/projectdiscovery/nuclei/v3
Same CWE
10 shownCWE-78
Frequently asked(5)
What is CVE-2026-76802?
CVE-2026-76802 is a medium vulnerability published on September 22, 2026. Nuclei is a vulnerability scanner built on a simple YAML-based DSL. From 3.0.0 until 3.10.0, the DAST template loading branch does not apply the unsigned code-template signature check before accepting a template that contains both a fuzzing: block and an unsigned code: block. When an operator…
When was CVE-2026-76802 disclosed?
CVE-2026-76802 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76802 actively exploited?
CVE-2026-76802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.2% of all scored CVEs.
What is the CVSS score of CVE-2026-76802?
CVE-2026-76802 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-76802?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76802, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76802
Is Your Infrastructure Affected by CVE-2026-76802?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.