CVE-2026-76819 Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability
Not scored
Published
Updated
Check this codebase for CVE-2026-76819 and fix it if it is affected.
What it is: CVE-2026-76819 is a vulnerability in github.com/projectdiscovery/nuclei, published on 22 Sep 2026.
Exploitation: There is no known exploitation of CVE-2026-76819 in the wild and no public exploit code.
Affected packages and fixed versions:
- github.com/projectdiscovery/nuclei/v3 (Go): affected from 3.0.0; fixed in 3.10.0
- github.com/projectdiscovery/nuclei/v3 (Go): affected from 3.0.0; fixed in 3.10.0
- github.com/projectdiscovery/nuclei/v3 (Go): affected from 3.0.0; fixed in 3.10.0
- github.com/projectdiscovery/nuclei (Go): affected all versions; no fix listed
- github.com/projectdiscovery/nuclei/v2 (Go): affected all versions; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-76819/ (Markdown: https://insights.sbomify.com/CVE-2026-76819/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-76819?
CVE-2026-76819 is a vulnerability in github.com/projectdiscovery/nuclei, published on 22 Sep 2026.
Official description
Further research determined the issue results from a dependency.
Which versions are affected by CVE-2026-76819?
5 open source packages ship an affected version, including github.com/projectdiscovery/nuclei/v3, github.com/projectdiscovery/nuclei and github.com/projectdiscovery/nuclei/v2.
| Package | Affected | Fixed in |
|---|---|---|
github.com/projectdiscovery/nuclei/v3 Go | From 3.0.0 | 3.10.0 |
github.com/projectdiscovery/nuclei/v3 Go | From 3.0.0 | 3.10.0 |
github.com/projectdiscovery/nuclei/v3 Go | From 3.0.0 | 3.10.0 |
github.com/projectdiscovery/nuclei Go | All versions | None |
github.com/projectdiscovery/nuclei/v2 Go | All versions | None |
How do I fix CVE-2026-76819?
Upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0 or later.
Is CVE-2026-76819 being exploited?
There is no known exploitation of CVE-2026-76819 in the wild and no public exploit code.
Sources
Also known as GHSA-vxg7-f2jj-jmqm, GO-2026-6575.