Nuclei: Local File Read via Workflow File-Protocol Gate Bypass

Exploitation

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

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-76804: 0.17% estimated exploitation activity in the next 30 days; percentile 5.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.

A vulnerability in Nuclei's workflow template loader allows file: protocol templates to execute without the -file flag, bypassing a security gate that is meant to prevent local file reads on the scanner host. Affected Component The issue is in the workflow template loading path. The main template loader enforces the -file gate for file-protocol templates, but the workflow loader did not apply the same check when resolving templates referenced by a workflow. Description Nuclei disables file-protocol templates by default because they read local files from the host running the scanner. Operators must explicitly enable them with the -file flag. When a workflow references a file-protocol template, the workflow loader accepted and executed that template without verifying that -file was enabled. Because workflows run unsigned by default, an untrusted workflow could load and execute a file-protocol template and read local files from the scan target path, even though the operator had not…

Published by the source

22 Sep 2026, 20:37 UTC

Last modified by the source

1 Oct 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qgw5-7j4f-fg97

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6574

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qgw5-7j4f-fg97

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

# Patch Next advisory brief: CVE-2026-76804

Advisory: Nuclei: Local File Read via Workflow File-Protocol Gate Bypass
IDs: CVE-2026-76804, GHSA-qgw5-7j4f-fg97
Record: https://patchnext.com/advisories/cve-2026-76804 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/projectdiscovery/nuclei/v3 3.10.0. A vendor fix does not mean a deployment is fixed.

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

## Suggested inspection (read-only)
- Go github.com/projectdiscovery/nuclei: check the installed version with your package manager.
- Go github.com/projectdiscovery/nuclei/v3: check the installed version with your package manager.
- Go github.com/projectdiscovery/nuclei/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/projectdiscovery/nuclei, github.com/projectdiscovery/nuclei/v3, github.com/projectdiscovery/nuclei/v2.
- 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://osv.dev/vulnerability/GO-2026-6574 (OSV record GO-2026-6574 lists affected ranges: Go github.com/projectdiscovery/nuclei >=0; Go github.com/projectdiscovery/nuclei/v2 >=0; Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-qgw5-7j4f-fg97 (OSV record GHSA-qgw5-7j4f-fg97 lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://github.com/advisories/GHSA-qgw5-7j4f-fg97 (GitHub-reviewed advisory GHSA-qgw5-7j4f-fg97 lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0)

Commands are suggestions: review each one before running it.