PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-92718 projectdiscovery CVE debrief

CVE-2026-92718 Nuclei Template Signature Verification Bypass. Nuclei versions before 3.11.1 are vulnerable to a template signature verification bypass due to caching based solely on file modification time without content checksums. This allows attackers to replace verified templates with unsigned malicious content and restore the original modification time, potentially leading to arbitrary code execution. Defenders should assess exposure, prioritize updating to version 3.11.1 or later, and inventory their deployments. Security teams and Nuclei users should be aware of the potential for attackers to exploit this vulnerability.

Vendor
projectdiscovery
Product
nuclei
CVSS
HIGH 7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-18
Advisory published
2026-09-16
Advisory updated
2026-09-18

Who should care

Defenders responsible for Nuclei installations, particularly those using versions before 3.11.1, should assess exposure and prioritize updating to the latest version. Security teams and Nuclei users should be aware of the potential for attackers to exploit this vulnerability, leading to possible code execution.

Why it matters

CVE-2026-92718 is a high-severity vulnerability in Nuclei that allows attackers to bypass template signature verification, potentially leading to arbitrary code execution. Defenders should prioritize updating Nuclei installations to version 3.11.1 or later and inventory their deployments to assess exposure.

  • Potential execution of arbitrary operating system commands due to bypassed template signature verification.
  • Possible compromise of Nuclei installations through malicious template replacements.
  • Need for verification of Nuclei version and inventory of installations to identify exposure.
  • Priority on updating Nuclei to version 3.11.1 or later to mitigate the vulnerability.

Technical summary

Nuclei versions before 3.11.1 are vulnerable to a template signature verification bypass. The vulnerability arises from the reliance on file modification time alone for caching template signature verification, without considering content checksums. This allows attackers to replace verified templates with unsigned malicious content and restore the original modification time, effectively bypassing signature checks and potentially leading to the execution of arbitrary operating system commands.

Defensive priority

High

Recommended defensive actions

  • Review and update Nuclei to version 3.11.1 or later to ensure template signature verification is properly enforced.
  • Inventory Nuclei installations to identify potential exposure.
  • Monitor for suspicious template usage or modifications.
  • Verify Nuclei version and assess exposure in your environment.
  • Implement compensating controls for exposed systems while remediation is scheduled and verified.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Nuclei versions before 3.11.1, where template signature verification is bypassed due to reliance on file modification time without content checksums.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-92718 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-92718

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-92718 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92718

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.