Nuclei Template Signature Verification Bypass

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2024-43405: 1.11% estimated exploitation activity in the next 30 days; percentile 65.94 (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 A vulnerability has been identified in Nuclei's template signature verification system that could allow an attacker to bypass the signature check and possibly execute malicious code via custom code template. Affected Component The vulnerability is present in the template signature verification process, specifically in the signer package. Description The vulnerability stems from a discrepancy between how the signature verification process and the YAML parser handle newline characters, combined with the way multiple signatures are processed. This allows an attacker to inject malicious content into a template while maintaining a valid signature for the benign part of the template. Affected Users 1. CLI Users: Those executing custom code templates from unverified sources. This includes templates authored by third parties or obtained from unverified repositories. 2. SDK Users: Developers integrating Nuclei into their platforms, particularly if they permit the execution of custom…

Published by the source

4 Sep 2024, 17:38 UTC

Last modified by the source

14 Oct 2024, 14:19 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7h5p-mmpp-hgmm

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

# Patch Next advisory brief: CVE-2024-43405

Advisory: Nuclei Template Signature Verification Bypass
IDs: CVE-2024-43405, GHSA-7h5p-mmpp-hgmm
Record: https://patchnext.com/advisories/cve-2024-43405 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
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.2. A vendor fix does not mean a deployment is fixed.

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

## 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-7h5p-mmpp-hgmm (GitHub-reviewed advisory GHSA-7h5p-mmpp-hgmm lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.3.2)

Commands are suggestions: review each one before running it.