Nuclei Security Update Addresses 5 Vulnerabilities
Tech GuruQuick Answer
Nuclei 3.10.0 fixes five issues affecting the scanner host in versions 3.0.0 through releases before 3.10.0. Untrusted templates can cross code or local-file boundaries; a separate DAST/fuzz issue can disclose environment variables when that option is enabled. Inventory CLI binaries, CI images and SDK consumers, not only the template repository. Upgrade the engine and keep scans confined to authorized targets and trusted templates.
Confirm Scope And Apply The Supported Fix
What to do now: stop untrusted template/workflow execution on affected engines, identify DAST and environment-variable settings, and update binaries plus embedded SDK builds through the project channel. Keep scanner credentials and host mounts limited; an engine upgrade does not revoke secrets that may already have been exposed.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | Nuclei packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-vxg7-f2jj-jmqm / GHSA-jpf4-98qj-qr67 / GHSA-xhmx-w2j4-rw3q / GHSA-qgw5-7j4f-fg97 / GHSA-jpvm-9frm-hjcq |
| CVEs | CVE-2026-76802, CVE-2026-76803, CVE-2026-76804, CVE-2026-76805, CVE-2026-76819 |
| Authoritative release date | 2026-07-16 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-08-19, 2026-08-20 UTC (project advisory dates, not database ingestion) |
| Affected versions | github.com/projectdiscovery/nuclei/v3 >= 3.0.0, < 3.10.0 |
| Fixed version | github.com/projectdiscovery/nuclei/v3 3.10.0 |
| CVSS base score | 4.7 / 5.3 / 5.5 / 8.6 (CVSS v3) |
| CVSS severity | Medium to High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The Goja flaw can execute native code through untrusted JavaScript templates without the -code flag. The DAST loader issue bypasses code-template signature and flag checks when -dast is enabled. The MySQL and workflow paths bypass local-file restrictions under their documented conditions. Environment disclosure is narrower: it requires response-derived data in DAST/fuzz processing with -env-vars/-ev explicitly enabled. The Goja advisory identifies JavaScript-template signing in 3.11.0 as additional hardening, distinct from its 3.10.0 engine fix.
What To Validate Now
- Inventory. Record each CLI/SDK engine version, template/workflow sources, DAST settings, environment-variable inclusion, scanner credentials and filesystem mounts.
- Establish applicability. Match engine versions from 3.0.0 up to, but excluding, 3.10.0 and the specific mode/input conditions. Leaving
-code,-fileor-lfadisabled is not a comprehensive workaround for these bypasses. - Remediate. Apply github.com/projectdiscovery/nuclei/v3 3.10.0 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Use an isolated runner with synthetic data and an authorized local target to check normal trusted scans and rejection of prohibited template capabilities. Record the running engine version and flags; updating templates alone is not the engine fix.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Do not run published exploit templates against production scanners or third-party targets to prove applicability. Disable environment-variable inclusion for untrusted DAST targets while arranging the fix, and avoid untrusted JavaScript/workflow inputs. If disclosure or host compromise is suspected, preserve evidence and handle credential revocation and runner rebuild separately from the package update.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
