Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.7 · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-76802: 0.18% estimated exploitation activity in the next 30 days; percentile 7.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability in Nuclei's DAST template loading path allows unsigned code: protocol templates to execute, bypassing the cryptographic signature requirement that is meant to prevent arbitrary command execution from untrusted templates. Affected Component The issue is in the template loader's DAST loading branch. When -dast is enabled and a template contains a fuzzing: block, the loader accepted the template through a code path that omitted the unsigned-code-template signature check present in the normal loading branch. Description Nuclei requires code: protocol templates to be cryptographically signed before execution. Unsigned code templates are normally skipped with a warning. However, when a template combined a fuzzing: block (making it DAST-eligible) with an unsigned code: block, enabling -dast routed the template through the DAST loader branch, which did not enforce signature verification. For multiprotocol templates containing both HTTP and code: blocks, the unsigned code…

Published by the source

22 Sep 2026, 20:37 UTC

Last modified by the source

1 Oct 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jpf4-98qj-qr67

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6570

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jpf4-98qj-qr67

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-76802

Advisory: Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass
IDs: CVE-2026-76802, GHSA-jpf4-98qj-qr67
Record: https://patchnext.com/advisories/cve-2026-76802 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/projectdiscovery/nuclei/v3 3.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectdiscovery/nuclei: affected every version
- Go github.com/projectdiscovery/nuclei/v3: affected >= 3.0.0, < 3.10.0; fixed in 3.10.0
- Go github.com/projectdiscovery/nuclei/v2: affected every version

## Suggested inspection (read-only)
- Go github.com/projectdiscovery/nuclei: check the installed version with your package manager.
- Go github.com/projectdiscovery/nuclei/v3: check the installed version with your package manager.
- Go github.com/projectdiscovery/nuclei/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/projectdiscovery/nuclei, github.com/projectdiscovery/nuclei/v3, github.com/projectdiscovery/nuclei/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jpf4-98qj-qr67 (OSV record GHSA-jpf4-98qj-qr67 lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6570 (OSV record GO-2026-6570 lists affected ranges: Go github.com/projectdiscovery/nuclei >=0; Go github.com/projectdiscovery/nuclei/v2 >=0; Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jpf4-98qj-qr67 (GitHub-reviewed advisory GHSA-jpf4-98qj-qr67 lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0)

Commands are suggestions: review each one before running it.