CVE-2026-76819: Rejected reason: Further research determined the issue results from a dependency.

CVE-2026-76819 · Severity: high · CVSS 8.6 · Published 2026-09-22

Nuclei is a security scanner that executes JavaScript templates to test web applications and infrastructure. A memory safety vulnerability in its embedded JavaScript engine allows attackers to craft malicious templates that execute arbitrary native code on the scanner host, potentially compromising the entire system. This affects users running untrusted templates from third-party sources or plugin platforms.

Technologies: github.com/projectdiscovery/nuclei (Go), github.com/projectdiscovery/nuclei/v2 (Go), github.com/projectdiscovery/nuclei/v3 (Go), ProjectDiscovery Nuclei. Vendors: Go, ProjectDiscovery.

Quick answers

Is CVE-2026-76819 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-76819 being exploited in the wild.
How severe is CVE-2026-76819?
High severity, with a CVSS score of 8.6, published 22 September 2026.
Which products and versions are affected?
github.com/projectdiscovery/nuclei (Go) SEMVER:introduced=0; github.com/projectdiscovery/nuclei/v2 (Go) SEMVER:introduced=0; github.com/projectdiscovery/nuclei/v3 (Go) >= 3.0.0, < 3.10.0, SEMVER:introduced=3.0.0,fixed=3.10.0; ProjectDiscovery Nuclei before 3.10.0.
Is there a fix for CVE-2026-76819?
Yes. github.com/projectdiscovery/nuclei/v3 (Go): upgrade to 3.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-76819 attacked?
It is attacked over the network.
Am I affected by CVE-2026-76819?
Check whether you run github.com/projectdiscovery/nuclei (Go), github.com/projectdiscovery/nuclei/v2 (Go), github.com/projectdiscovery/nuclei/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/projectdiscovery/nuclei/v3 (Go): upgrade to 3.10.0 or later
    go get github.com/projectdiscovery/nuclei/v3@v3.10.0

Technical details

The vulnerability is an out-of-bounds heap write in the Goja JavaScript runtime (pkg/js/) that Nuclei uses to execute `javascript:` protocol templates. Attackers can craft JavaScript code within templates that corrupts heap memory to achieve native code execution. No authentication or special flags are required—unsigned `javascript:` templates execute by default, and the vulnerability can be triggered through template initialization (`init` section) before other security checks complete. The attack vector is network-accessible if templates come from remote sources. Nuclei v3.10.0 patches the issue by updating the Goja dependency; v3.11.0 adds cryptographic signing requirements for JavaScript templates as additional defense in depth.

Affected products

  • ProjectDiscovery Nuclei before 3.10.0

Identifiers

  • CVE-2026-76819
  • GHSA-vxg7-f2jj-jmqm
  • GO-2026-6575

Timeline

  • 2026-09-22: disclosed: Published via GitHub Security Advisory GHSA-vxg7-f2jj-jmqm
  • 2026-09-22: patched: Fixed in Nuclei v3.10.0 by updating Goja dependency (PR #7467)
  • 2026-09-22: other: Additional hardening in v3.11.0 with JavaScript template signing requirement (PR #7514)

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.