CVE-2026-76802: Nuclei Arbitrary Command Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-jpf4-98qj-qr67
CVSS 4.7
CWE-78
Published
Advisory Summary

CVE-2026-76802 is a MODERATE (CVSS 4.7) arbitrary command execution vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Nuclei libraries in the Go ecosystem. The issue involves arbitrary command execution via dast code signature bypass. Remediation is available by upgrading affected packages to version 3.10.0.

CVE-2026-76802 at a Glance

CVE Identifier CVE-2026-76802
GHSA Identifier GHSA-jpf4-98qj-qr67
Severity MODERATE
CVSS v3.1 Base Score 4.7
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Nuclei
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-76802

To remediate this vulnerability, upgrade all affected Nuclei dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/projectdiscovery/nuclei/v3 fixed: 3.10.0
Upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/projectdiscovery/nuclei/v3

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-76802, inspect your project dependencies for Nuclei:

inspect dependencies for github.com/projectdiscovery/nuclei/v3

Analyze the terminal output to locate any version of Nuclei in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.10.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Nuclei, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-76802 Affected Nuclei Versions

1 component(s)
Fixed Versions:
3.10.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/projectdiscovery/nuclei/v3
Go
≥ 3.0.0
< 3.10.0
3.10.0

References

Frequently Asked Questions

What is CVE-2026-76802?
CVE-2026-76802 is a security vulnerability in Nuclei involving Arbitrary Command Execution via DAST Code Signature Bypass under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Nuclei versions are affected?
Affected versions include releases prior to 3.10.0 across affected packages: github.com/projectdiscovery/nuclei/v3.
What version fixes CVE-2026-76802?
Upgrading to 3.10.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/projectdiscovery/nuclei/v3 affected?
Yes, github.com/projectdiscovery/nuclei/v3 is affected in releases prior to 3.10.0. Upgrade your dependency to 3.10.0 or later.
What is the CVSS score of CVE-2026-76802?
CVE-2026-76802 has a CVSS v3.1 base score of 4.7 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-76802?
CVE-2026-76802 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check Go dependencies for CVE-2026-76802?
Run the dependency tree command: 'inspect dependencies for github.com/projectdiscovery/nuclei/v3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jpf4-98qj-qr67",
  "modified" : "2026-09-22T20:37:16Z",
  "published" : "2026-09-22T20:37:16Z",
  "aliases" : [ "CVE-2026-76802" ],
  "summary" : "Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass",
  "details" : "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.\n\n**Affected Component**\n\nThe 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.\n\n**Description**\n\nNuclei 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.\n\nFor 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.\n\n> [!NOTE]\nBoth 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.\n\n**Affected Users**\n\n- **CLI users** running DAST/fuzzing scans (`-dast`) with untrusted or attacker-supplied templates that contain both `fuzzing:` and `code:` blocks.\n- **SDK users** who integrate Nuclei with DAST mode enabled and allow end users to supply custom templates.\n\n**Patches**\n\n- The vulnerability is fixed in Nuclei v3.10.0. Upgrading is strongly recommended.\n- Fix reference: https://github.com/projectdiscovery/nuclei/pull/7472\n\n**Mitigation**\n\nUpgrade to Nuclei v3.10.0, where code template signature verification is enforced before DAST loading.\n\nIn the meantime, avoid running DAST scans with untrusted templates.\n\n**Workarounds**\n\nIf upgrading is not an option, do not use `-dast` with templates from unverified sources.\n\n**Acknowledgments**\n\nThanks to @daffainfo for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/projectdiscovery/nuclei/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.10.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jpf4-98qj-qr67"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-76802"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/pull/7472"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/commit/1c440e755a97471c56fb0276ee8a8c4132974645"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/projectdiscovery/nuclei"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/releases/tag/v3.10.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-22T20:37:16Z",
    "nvd_published_at" : "2026-09-22T17:17:24Z"
  }
}