Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability

CVE-2026-76819GHSA-vxg7-f2jj-jmqm

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/projectdiscovery/nuclei

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/projectdiscovery/nuclei/v3

    Affected
    >= 3.0.0, < 3.10.0
    Fixed in
    3.10.0

  • Go github.com/projectdiscovery/nuclei/v2

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vxg7-f2jj-jmqm

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6575

  3. Revision 1 · created ·

    Published from osv record GHSA-vxg7-f2jj-jmqm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-76819

Advisory: Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability
IDs: CVE-2026-76819, GHSA-vxg7-f2jj-jmqm
Record: https://patchnext.com/advisories/cve-2026-76819 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/projectdiscovery/nuclei/v3 3.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectdiscovery/nuclei: affected every version
- Go github.com/projectdiscovery/nuclei/v3: affected >= 3.0.0, < 3.10.0; fixed in 3.10.0
- Go github.com/projectdiscovery/nuclei/v2: affected every version

## Suggested inspection (read-only)
- Go github.com/projectdiscovery/nuclei: check the installed version with your package manager.
- Go github.com/projectdiscovery/nuclei/v3: check the installed version with your package manager.
- Go github.com/projectdiscovery/nuclei/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/projectdiscovery/nuclei, github.com/projectdiscovery/nuclei/v3, github.com/projectdiscovery/nuclei/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6575 (OSV record GO-2026-6575 lists affected ranges: Go github.com/projectdiscovery/nuclei >=0; Go github.com/projectdiscovery/nuclei/v2 >=0; Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-vxg7-f2jj-jmqm (OSV record GHSA-vxg7-f2jj-jmqm lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://github.com/advisories/GHSA-vxg7-f2jj-jmqm (GitHub-reviewed advisory GHSA-vxg7-f2jj-jmqm lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0)

Commands are suggestions: review each one before running it.

Loading voting…