projectdiscovery/nuclei allows unsigned code template execution through workflows

Exploitation

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

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N · score source

EPSS

• CVE-2024-40641: 0.31% estimated exploitation activity in the next 30 days; percentile 24.04 (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.

Summary Find a way to execute code template without -code option and signature. Details write a code.yaml: using nc to listen on 80: execute PoC template with nuclei: and nc will get id command output. We use -w to specify a workflow file, not -t to template file. and notice there is a workflows field in code.yaml to pretend to be a workflow file. Test in Linux and Nuclei v3.2.9 Impact Some web applications inherit from Nuclei and allow users to edit and execute workflow files. In this case, users can execute arbitrary commands. (Although, as far as I know, most web applications use -t to execute)

Published by the source

17 Jul 2024, 19:32 UTC

Last modified by the source

6 Aug 2024, 05:04 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c3q9-c27p-cw9h

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

# Patch Next advisory brief: CVE-2024-40641

Advisory: projectdiscovery/nuclei allows unsigned code template execution through workflows
IDs: CVE-2024-40641, GHSA-c3q9-c27p-cw9h
Record: https://patchnext.com/advisories/cve-2024-40641 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/projectdiscovery/nuclei/v3 3.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectdiscovery/nuclei/v3: affected < 3.3.0; fixed in 3.3.0

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/projectdiscovery/nuclei/v3.
- 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://github.com/advisories/GHSA-c3q9-c27p-cw9h (GitHub-reviewed advisory GHSA-c3q9-c27p-cw9h lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=0 <3.3.0)

Commands are suggestions: review each one before running it.