Code Injection in github.com/projectdiscovery/nuclei/v3 (CVE-2026-41282)
Summary
Code injection in github.com/projectdiscovery/nuclei/v3 (CVE-2026-41282). Confidential information can be exposed externally. Exploitable via EnvironmentVariables. Mitigation: upgrade to 3.8.0 or later.
Original description
The description as published by the source.
Nuclei is a vulnerability scanner built on a simple YAML-based DSL. From version 3.0.0 to before version 3.8.0, a vulnerability in Nuclei's expression evaluation engine makes it possible for a malicious target server to inject and execute supported DSL expressions. This happens when HTTP response data containing helper/function syntax gets reused by multi-step templates. If the -env-vars / -ev option is explicitly enabled, this can expose host environment variables. That option is off by default, so standard configurations are not affected by the information disclosure risk. This issue has been patched in version 3.8.0.
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-41282 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-41282" on the vendor's site.
CVE-2026-41282 (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.
Arbitrary code execution (CWE-94) exists in github.com/projectdiscovery/nuclei/v3. Attackers reach the vulnerable code path via EnvironmentVariables without authentication.
Check the vendor advisory for the affected versions of github.com/projectdiscovery/nuclei/v3. Attack surface: EnvironmentVariables / true.
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.
Update to 3.8.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.8.0ステージング環境で 3.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com