Vulnerability in github.com/projectdiscovery/nuclei/v3 (CVE-2026-76803)
Summary
Vulnerability in github.com/projectdiscovery/nuclei/v3 (CVE-2026-76803). Confidential information can be exposed externally. Exploitable via allowAllFiles. Mitigation: upgrade to 3.10.0 or later.
Original description
The description as published by the source.
A vulnerability in Nuclei's JavaScript MySQL client library allows arbitrary local file reads that bypass the -allow-local-file-access (-lfa) sandbox restriction.
Affected Component
The issue is in the nuclei/mysql JavaScript library used by javascript: protocol templates. The MySQL client connection logic did not enforce the local file access sandbox when handling the allowAllFiles DSN parameter used by LOAD DATA LOCAL INFILE.
Description
Without -lfa, Nuclei confines local file access to the templates directory. However, a javascript: template could connect to a MySQL server with allowAllFiles=true in the connection DSN. With this option enabled, a malicious MySQL server can issue LOAD DATA LOCAL INFILE requests for arbitrary paths on the scanner host. The MySQL client reads the full file contents and sends them to the server, bypassing the same sandbox that blocks direct filesystem reads through other APIs.
javascript: templates execute without the -code flag and unsigned javascript: templates run by default, making this reachable from untrusted third-party templates when scanning attacker-controlled MySQL endpoints.
[!NOTE]
The-allow-local-file-access(-lfa) option is off by default. This issue allows bypassing that restriction, not merely expanding an already-enabled capability.
Affected Users
- CLI users running untrusted or third-party
javascript:templates against MySQL-compatible targets. - SDK users who…
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-76803 has been found in github.com/projectdiscovery/nuclei/v3.
Attackers can target a specific entry point like allowAllFiles over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/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-76803" on the vendor's site.
CVE-2026-76803 (github.com/projectdiscovery/nuclei/v3) — CWE-284 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: allowAllFiles
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.
A vulnerability (CWE-284) exists in github.com/projectdiscovery/nuclei/v3. Attackers reach the vulnerable code path via allowAllFiles without authentication.
Check the vendor advisory for the affected versions of github.com/projectdiscovery/nuclei/v3. Attack surface: allowAllFiles.
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.
Update to 3.10.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0ステージング環境で 3.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com