# CVE-2026-92718: Nuclei from 3.7.0 before 3.11.1 Template Signature Bypass via Modification-Time-Only Cache

> Attackers can bypass template signature checks in Nuclei by modifying files while preserving timestamps, leading to arbitrary command execution.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-77rj-h8wx-6cgq

## What is CVE-2026-92718?

CVE-2026-92718 is a high-severity vulnerability in projectdiscovery nuclei, published on 16 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Nuclei versions before 3.11.1 cache template signature verification based only on file modification time without content checksums. Attackers can replace verified templates with unsigned malicious content and restore the original modification time to bypass signature checks and execute arbitrary operating system commands.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-92718?


## How do I fix CVE-2026-92718?

No fix has been published for CVE-2026-92718 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92718 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92718 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92718 and fix it if it is affected.

What it is: CVE-2026-92718 is a high-severity vulnerability in projectdiscovery nuclei, published on 16 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92718 exists.

Affected product: projectdiscovery nuclei. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92718/ (Markdown: https://insights.sbomify.com/CVE-2026-92718/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92718
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92718
- OSV: https://osv.dev/vulnerability/CVE-2026-92718

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92718/
Summaries are generated and may contain mistakes; the official description above is the record.