Live › vulnerability › CVE-2026-76802
Go to dashboardNuclei, a Go vulnerability scanner, skips its unsigned code-template signature check when DAST is enabled and loads a template that contains a fuzzing block with an unsigned code block. An attacker who can supply a template can run arbitrary shell commands on the host running the scan.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/projectdiscovery/nuclei | go | all versions | – |
| github.com/projectdiscovery/nuclei/v2 | go | all versions | – |
| github.com/projectdiscovery/nuclei/v3 | go | >= 3.0.0, < 3.10.0 | 3.10.0 |
3.0.0 up to but not including 3.10.03.10.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-76802")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.