Vulnerability-Lookup

GHSA-JPF4-98QJ-QR67

Vulnerability from github – Published: 2026-09-22 20:37 – Updated: 2026-09-22 20:37

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.

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.

Severity

4.7 (Medium)


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

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/projectdiscovery/nuclei/v3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.0.0"
            },
            {
              "fixed": "3.10.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-76802"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-78"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-22T20:37:16Z",
    "nvd_published_at": "2026-09-22T17:17:24Z",
    "severity": "MODERATE"
  },
  "details": "A vulnerability in Nuclei\u0027s 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\u0027s 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\u003e [!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.",
  "id": "GHSA-jpf4-98qj-qr67",
  "modified": "2026-09-22T20:37:16Z",
  "published": "2026-09-22T20:37:16Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass"
}

CVE-2026-76802 (GCVE-0-2026-76802)

Vulnerability from cvelistv5 – Published: 2026-09-22 16:47 – Updated: 2026-09-22 17:04

Title

Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass

Summary

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.

Severity

4.7 (Medium)


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

SSVC

Exploitation: none Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2026-09-22 17:01 UTC

CWE

CWE-78 - Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Assigner

GitHub_M mitre root Scorecard

References

4 references

URL	Tags
https://github.com/projectdiscovery/nuclei/securi…	x_refsource_CONFIRM
https://github.com/projectdiscovery/nuclei/pull/7472	x_refsource_MISC
https://github.com/projectdiscovery/nuclei/commit…	x_refsource_MISC
https://github.com/projectdiscovery/nuclei/releas…	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
projectdiscovery	nuclei	Affected: >= 3.0.0, < 3.10.0

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-76802",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-22T17:01:01.338492Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-09-22T17:04:53.745Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "nuclei",
          "vendor": "projectdiscovery",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 3.0.0, \u003c 3.10.0"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "LOCAL",
            "availabilityImpact": "NONE",
            "baseScore": 4.7,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-78",
              "description": "CWE-78: Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-22T16:47:00.360Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jpf4-98qj-qr67",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jpf4-98qj-qr67"
        },
        {
          "name": "https://github.com/projectdiscovery/nuclei/pull/7472",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/projectdiscovery/nuclei/pull/7472"
        },
        {
          "name": "https://github.com/projectdiscovery/nuclei/commit/1c440e755a97471c56fb0276ee8a8c4132974645",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/projectdiscovery/nuclei/commit/1c440e755a97471c56fb0276ee8a8c4132974645"
        },
        {
          "name": "https://github.com/projectdiscovery/nuclei/releases/tag/v3.10.0",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/projectdiscovery/nuclei/releases/tag/v3.10.0"
        }
      ],
      "source": {
        "advisory": "GHSA-jpf4-98qj-qr67",
        "discovery": "UNKNOWN"
      },
      "title": "Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-76802",
    "datePublished": "2026-09-22T16:47:00.360Z",
    "dateReserved": "2026-08-19T19:52:28.212Z",
    "dateUpdated": "2026-09-22T17:04:53.745Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-JPF4-98QJ-QR67

CVE-2026-76802 (GCVE-0-2026-76802)

Tags

Sightings

Nomenclature

Related by attack behaviour