Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Check if your repositories are affected!View on GitHub
Search

GHSA-jpf4-98qj-qr67

MediumCVSS 4.7 / 10
Published Sep 22, 2026·Last modified Sep 22, 2026
Affected Components(1)
Go logogithub.com/projectdiscovery/nuclei/v3
3.0.0 – 3.10.0
Description

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 request was included in the execution queue regardless of whether -code was set. This allowed arbitrary shell command execution from an unsigned code: block with only -dast enabled.

[!NOTE] Both DAST mode (-dast) and code-protocol templates are disabled by default. Code templates normally require both the -code flag and a valid template signature. This issue bypassed the signature and -code controls only when -dast was explicitly enabled.

Affected Users

  • CLI users running DAST/fuzzing scans (-dast) with untrusted or attacker-supplied templates that contain both fuzzing: and code: blocks.
  • SDK users who integrate Nuclei with DAST mode enabled and allow end users to supply custom templates.

Patches

  • The vulnerability is fixed in Nuclei v3.10.0. Upgrading is strongly recommended.
  • Fix reference: https://github.com/projectdiscovery/nuclei/pull/7472

Mitigation

Upgrade to Nuclei v3.10.0, where code template signature verification is enforced before DAST loading.

In the meantime, avoid running DAST scans with untrusted templates.

Workarounds

If upgrading is not an option, do not use -dast with templates from unverified sources.

Acknowledgments

Thanks to @daffainfo for reporting this issue.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
4.7

The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a high impact on the integrity of the data.

Threat Intelligence
4.3

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
0.18%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities

Browse More

Medium severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard