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.
CVE-2026-92718
HIGHPre-NVD 7.37.3—Trending — 4 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. a secondary CVSS source baseline 7.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 49(Track*)EG Risk 49/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
Advisory Details (6)
Auto-updated Sep 16, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
Nuclei from 3.7.0 before 3.11.1 Template Signature Bypass via Modification-Time-Only Cache | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nuclei-from-3.7.0-before-3.11.1-template-signature-bypass-via-modification-time-only-cachegithub_commit
commit 9de96e4dda5a (projectdiscovery/nuclei)
Fix landed in projectdiscovery/nuclei commit 9de96e4dda5a — awaiting tagged release
https://github.com/projectdiscovery/nuclei/commit/9de96e4dda5a03da963b9ae6582f03ea55791a76generic
nuclei/pkg/catalog/index/metadata.go at v3.11.0 · projectdiscovery/nuclei · GitHub
https://github.com/projectdiscovery/nuclei/blob/v3.11.0/pkg/catalog/index/metadata.go#L78-L84generic
nuclei/pkg/templates/compile.go at v3.11.0 · projectdiscovery/nuclei · GitHub
https://github.com/projectdiscovery/nuclei/blob/v3.11.0/pkg/templates/compile.go#L610-L624generic
GitHub - projectdiscovery/nuclei: Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations. · GitHub
https://github.com/projectdiscovery/nucleigeneric
[BUG] Nuclei template signature bypass: mtime-only metadata cache runs unsigned code templates · Issue #7663 · projectdiscovery/nuclei · GitHub
https://github.com/projectdiscovery/nuclei/issues/7663Vendor Advisories for CVE-2026-92718(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 18:02 UTCGHSA enrichment
- 2026-09-19 06:49 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEG score recompute
- 2026-09-18 19:28 UTCGHSA enrichment
- 2026-09-18 18:34 UTCEG score recompute
- 2026-09-18 18:34 UTCGHSA enrichment
- 2026-09-18 16:45 UTCGHSA enrichment
- 2026-09-18 05:32 UTCEG score recompute
- 2026-09-18 05:32 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 18:18 UTCGHSA enrichment
- 2026-09-17 05:37 UTCEG score recompute
- 2026-09-17 05:37 UTCGHSA enrichment
- 2026-09-16 18:24 UTCEG score recompute
- 2026-09-16 17:38 UTCEG score recompute
- 2026-09-16 17:34 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-92718?
CVE-2026-92718 is a high vulnerability published on September 16, 2026. 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…
When was CVE-2026-92718 disclosed?
CVE-2026-92718 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92718 actively exploited?
CVE-2026-92718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.6% of all scored CVEs.
What is the CVSS score of CVE-2026-92718?
CVE-2026-92718 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-92718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92718, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92718
Is Your Infrastructure Affected by CVE-2026-92718?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.