Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-76804 medium CVSS 5.5

Vulnerability in github.com/projectdiscovery/nuclei/v3 (CVE-2026-76804)

Summary

Vulnerability in github.com/projectdiscovery/nuclei/v3 (CVE-2026-76804). Confidential information can be exposed externally. Mitigation: upgrade to 3.10.0 or later.

Original description

The description as published by the source.

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 enabled file templates.

[!NOTE]
File-protocol templates are disabled by default. This issue only affects users who run workflows from untrusted sources without having explicitly enabled -file.

Affected Users

  • CLI users running workflows (-w) that reference file-protocol templates from untrusted or third-party sources.
  • SDK users who integrate Nuclei into platforms where end users can supply workflow files and rely on the default -file restriction to bloc…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-76804 has been found in github.com/projectdiscovery/nuclei/v3.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0 or later.
If unsure, ask your IT team or search "github.com/projectdiscovery/nuclei/v3 CVE-2026-76804" on the vendor's site.

CVE-2026-76804 (github.com/projectdiscovery/nuclei/v3) — CWE-284 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 3.10.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-284) exists in github.com/projectdiscovery/nuclei/v3.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/projectdiscovery/nuclei/v3.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.10.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/projectdiscovery/nuclei/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/projectdiscovery/nuclei/v3' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/projectdiscovery/nuclei/v3 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0

    ステージング環境で 3.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/projectdiscovery/nuclei/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details