# CVE-2026-76802: Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass

> Attackers can execute arbitrary shell commands by supplying malicious templates when DAST mode is enabled, bypassing signature checks.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-jpf4-98qj-qr67, GO-2026-6570

## What is CVE-2026-76802?

CVE-2026-76802 is a medium-severity command injection vulnerability in projectdiscovery nuclei, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-76802?

5 open source packages ship an affected version, including github.com/projectdiscovery/nuclei/v3, github.com/projectdiscovery/nuclei and github.com/projectdiscovery/nuclei/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/projectdiscovery/nuclei/v3` | Go | From 3.0.0 | 3.10.0 |
| `github.com/projectdiscovery/nuclei/v3` | Go | From 3.0.0 | 3.10.0 |
| `github.com/projectdiscovery/nuclei/v3` | Go | From 3.0.0 | 3.10.0 |
| `github.com/projectdiscovery/nuclei` | Go | All versions | None |
| `github.com/projectdiscovery/nuclei/v2` | Go | All versions | None |

## How do I fix CVE-2026-76802?

Upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0 or later.

## Is CVE-2026-76802 being exploited?

There is no known exploitation of CVE-2026-76802 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76802 and fix it if it is affected.

What it is: CVE-2026-76802 is a medium-severity command injection vulnerability in projectdiscovery nuclei, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-76802 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/projectdiscovery/nuclei/v3 (Go): affected from 3.0.0; fixed in 3.10.0
- github.com/projectdiscovery/nuclei/v3 (Go): affected from 3.0.0; fixed in 3.10.0
- github.com/projectdiscovery/nuclei/v3 (Go): affected from 3.0.0; fixed in 3.10.0
- github.com/projectdiscovery/nuclei (Go): affected all versions; no fix listed
- github.com/projectdiscovery/nuclei/v2 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76802/ (Markdown: https://insights.sbomify.com/CVE-2026-76802/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76802
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76802
- OSV: https://osv.dev/vulnerability/CVE-2026-76802

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76802/
Summaries are generated and may contain mistakes; the official description above is the record.