← Back
CVE-2026-41645
medium
CVSS 5.3
Code Injection in github.com/projectdiscovery/nuclei/v3 (CVE-2026-41645)
Summary
code injection in github.com/projectdiscovery/nuclei/v3 (CVE-2026-41645). Confidential information can be exposed externally. Exploitable via ``EnvironmentVariables``. Mitigation: upgrade to `3.8.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41645** has been found in github.com/projectdiscovery/nuclei/v3.
Attackers can target a specific entry point like ``EnvironmentVariables`` 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.8.0** or later.
If unsure, ask your IT team or search "github.com/projectdiscovery/nuclei/v3 CVE-2026-41645" on the vendor's site.
CVE-2026-41645 (github.com/projectdiscovery/nuclei/v3) — CWE-94 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `EnvironmentVariables` / `true`
Patched: `3.8.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
**arbitrary code execution** (CWE-94) exists in github.com/projectdiscovery/nuclei/v3. Attackers reach the vulnerable code path via ``EnvironmentVariables`` without authentication.
📍 Affected scope
github.com/projectdiscovery/nuclei/v3 — . Attack surface: `EnvironmentVariables` / `true`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.8.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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/projectdiscovery/nuclei/v3 to 3.8.0ステージング環境で 3.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/projectdiscovery/nuclei/v3
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.8.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41645
- package https://github.com/projectdiscovery/nuclei
- web https://github.com/projectdiscovery/nuclei/commit/6c803c74d193f85f8a6d9803ce493fd302cad0eb
- web https://github.com/projectdiscovery/nuclei/commit/d2217320162d5782ca7cb95bef9dda17063818f3
- web https://github.com/projectdiscovery/nuclei/pull/7221
- web https://github.com/projectdiscovery/nuclei/pull/7321
- web https://github.com/projectdiscovery/nuclei/releases/tag/v3.8.0
- web https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jm34-66cf-qpvr
- web https://github.com/advisories/GHSA-jm34-66cf-qpvr