Skip to content

← Actionable
Medium, CVSS 5.3amended

Nuclei: Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode

CVE-2026-76805GHSA-jpvm-9frm-hjcq

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.

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
5.3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-76805: 0.41% estimated exploitation activity in the next 30 days; percentile 35.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A vulnerability in Nuclei's DAST/fuzz expression evaluation path allows a malicious target server to trigger disclosure of scanner-host environment variables when the -env-vars / -ev option is explicitly enabled. This is an incomplete fix for CVE-2026-41645 / GHSA-jm34-66cf-qpvr. The original fix hardened expressions.Evaluate() to be single-pass within one call, but did not address callers that invoked evaluation multiple times on substituted output in the DAST/fuzz pipeline. Affected Component The issue is in the DAST/fuzz payload evaluation path (pkg/fuzz/parts.go) and the shared template rendering boundary. When a multi-step template captures response data via an internal extractor and reuses it in a subsequent fuzz step, the fuzz evaluator could treat the substituted response content as fresh template syntax on a second evaluation pass. Description In DAST/fuzz mode, payload evaluation previously ran expression substitution more than once on the same value. Response-derived…

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

    Amended from ghsa record GHSA-jpvm-9frm-hjcq

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6571

  3. Revision 1 · created ·

    Published from osv record GHSA-jpvm-9frm-hjcq

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-76805

Advisory: Nuclei: Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode
IDs: CVE-2026-76805, GHSA-jpvm-9frm-hjcq
Record: https://patchnext.com/advisories/cve-2026-76805 (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: Medium (CVSS 5.3)
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/GHSA-jpvm-9frm-hjcq (OSV record GHSA-jpvm-9frm-hjcq lists affected ranges: Go github.com/projectdiscovery/nuclei/v3 >=3.0.0 <3.10.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6571 (OSV record GO-2026-6571 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://github.com/advisories/GHSA-jpvm-9frm-hjcq (GitHub-reviewed advisory GHSA-jpvm-9frm-hjcq 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…