Skip to main content
VulnerabilityPublished Updated

CVE-2026-76804: projectdiscovery nuclei · Improper Access Control

Affects projectdiscovery nucleiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 3.10.0 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.10.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade projectdiscovery nuclei to 3.10.0.

Affected software

ProductAffectedFixed in
projectdiscoverynucleiAffected
  • >=3.0.0 <3.10.0
Fixed in
  • 3.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Nuclei to version 3.10.0 or later, where the issue is fixed. Until then, avoid running untrusted unsigned workflows or workflows that reference file-protocol templates. Operators should be cautious when using the -w option or SDK integrations that accept end-user workflows and rely on default file access restrictions.

Description

Nuclei is a vulnerability scanner built on a simple YAML-based DSL. From 3.0.0 until 3.10.0, the workflow template loading path does not enforce the -file capability gate when resolving file: protocol templates referenced by a workflow. An untrusted unsigned workflow can therefore load a file-protocol template and read local files from the scanner host even when the operator has not enabled file templates. The issue affects CLI users running workflows with -w and SDK integrations that accept end-user workflows while relying on the default file-access restriction. This issue is fixed in version 3.10.0.

References

Community reviews

Loading reviews…