Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-76819

Code Injection in github.com/projectdiscovery/nuclei/v3 (CVE-2026-76819)

Summary

Code injection in github.com/projectdiscovery/nuclei/v3 (CVE-2026-76819). Risk of unauthorized operations or information disclosure. Exploitable via init. Mitigation: upgrade to 3.10.0 or later.

Original description

The description as published by the source.

A vulnerability in the Goja JavaScript engine used by Nuclei's javascript: protocol allows arbitrary native code execution on the scanner host when running untrusted JavaScript templates.

Affected Component

The issue is in the Goja JavaScript runtime embedded in Nuclei's JavaScript protocol (pkg/js/). An out-of-bounds heap write in the engine can be exploited to achieve native code execution during template evaluation.

Description

Nuclei uses the Goja engine to execute javascript: protocol templates. A memory safety vulnerability in Goja allows attacker-controlled JavaScript to corrupt heap memory and execute arbitrary native code on the host running Nuclei.

Because javascript: templates execute without the -code flag and unsigned JavaScript templates run by default, a malicious template from an untrusted source can trigger code execution during a normal scan. The vulnerability could also be reached through a template's init section, which runs during template initialization before other security checks complete.

[!NOTE]
JavaScript templates do not require the -code flag and are not subject to the code-template signing requirement on affected versions. Nuclei v3.11.0 adds a separate signing requirement for JavaScript templates as additional defense in depth.

Affected Users

  • CLI users running untrusted or third-party javascript: templates.
  • SDK users who integrate Nuclei into platforms where end users can supply JavaScript templa…

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-76819 has been found in github.com/projectdiscovery/nuclei/v3.
Attackers can target a specific entry point like init over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
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-76819" on the vendor's site.

CVE-2026-76819 (github.com/projectdiscovery/nuclei/v3) — CWE-94
Attack surface: init
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

Arbitrary code execution (CWE-94) exists in github.com/projectdiscovery/nuclei/v3. Attackers reach the vulnerable code path via init.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/projectdiscovery/nuclei/v3. Attack surface: init.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 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":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.10.0"}]}]
Go github.com/projectdiscovery/nuclei
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/projectdiscovery/nuclei/v2
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

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