Vulnerabilities in pkg:golang/github.com/projectdiscovery/nuclei/v3

PACKAGE
Advisory Identifier: GHSA-jpvm-9frm-hjcq
Advisory Summary

CVE-2026-76805 is a MODERATE (CVSS 5.3) environment variable disclosure vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Nuclei libraries in the Go ecosystem. The issue involves environment variable disclosure via response-derived data in dast/fuzz mode. Remediation is available by upgrading affected packages to version 3.10.0.

10 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/projectdiscovery/nuclei/v3

10 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/projectdiscovery/nuclei/v3. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-jpvm-9frm-hjcq CVE-2026-76805 MODERATE Nuclei: Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode
GHSA-qgw5-7j4f-fg97 CVE-2026-76804 MODERATE Nuclei: Local File Read via Workflow File-Protocol Gate Bypass
GHSA-xhmx-w2j4-rw3q CVE-2026-76803 MODERATE Nuclei: Local File Read via MySQL Client Sandbox Bypass
GHSA-jpf4-98qj-qr67 CVE-2026-76802 MODERATE Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass
GHSA-vxg7-f2jj-jmqm CVE-2026-76819 HIGH Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability
GHSA-29rg-wmcw-hpf4 CVE-2026-41646 MODERATE Nuclei: Local File Read via require() Module Loader Bypass
GHSA-jm34-66cf-qpvr CVE-2026-41645 MODERATE Nuclei: Environment variable disclosure via Response-Derived DSL Expressions
GHSA-7h5p-mmpp-hgmm CVE-2024-43405 MODERATE Nuclei Template Signature Verification Bypass
GHSA-w5wx-6g2r-r78q CVE-2024-27920 HIGH Nuclei allows unsigned code template execution through workflows
GHSA-c3q9-c27p-cw9h CVE-2024-40641 HIGH projectdiscovery/nuclei allows unsigned code template execution through workflows

CVE-2026-76805 at a Glance

CVE Identifier CVE-2026-76805
GHSA Identifier GHSA-jpvm-9frm-hjcq
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Nuclei
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-76805

To remediate this vulnerability, upgrade all affected Nuclei dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/projectdiscovery/nuclei/v3 fixed: 3.10.0
Upgrade github.com/projectdiscovery/nuclei/v3 to 3.10.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/projectdiscovery/nuclei/v3

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-76805, inspect your project dependencies for Nuclei:

inspect dependencies for github.com/projectdiscovery/nuclei/v3

Analyze the terminal output to locate any version of Nuclei in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.10.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Nuclei, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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](https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jm34-66cf-qpvr) / 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 content captured by an `internal: true` extractor in a prior protocol step could flow into a fuzz payload and be reinterpreted as DSL/helper syntax on a subsequent pass. When `-env-vars` (`-ev`) is enabled, environment variables are merged into the template variable map. A malicious target can return response data containing expressions like `{{env_var_name}}` which, when reused in a subsequent fuzz step, resolve to actual environment variable values. This can expose sensitive host data such as API keys, credentials, and tokens. Without `-ev` enabled (the default), response-derived data may still cause other DSL helpers to run, but that behavior is not treated as a security issue and has no meaningful security impact beyond unexpected behavior. > [!NOTE] The `-env-vars` / `-ev` option is off by default. Users who have not explicitly enabled it are not affected by this vulnerability. **Affected Users** - **CLI users** running `nuclei -dast` (or fuzzing) with multi-step templates that chain an internal extractor into a subsequent fuzz step against untrusted targets, with the `-ev` flag enabled. - **SDK users** who integrate Nuclei with the fuzz pipeline enabled, `EnvironmentVariables` set to `true`, and scan targets that are not fully trusted. **Patches** - The vulnerability is fixed in Nuclei v3.10.0. Upgrading is strongly recommended. - Fix reference: https://github.com/projectdiscovery/nuclei/pull/7499 - Related original fix: https://github.com/projectdiscovery/nuclei/pull/7221, https://github.com/projectdiscovery/nuclei/pull/7321 **Mitigation** Upgrade to Nuclei v3.10.0, where template-authored text is rendered once through a shared rendering boundary and runtime values from responses, extractors, and constants remain opaque data. If you have `-ev` enabled, disable it when scanning untrusted targets to avoid environment variable disclosure. **Workarounds** If upgrading is not an option, ensure `-env-vars` / `-ev` is not enabled when running DAST/fuzz scans with multi-step templates against untrusted targets. **Acknowledgments** Thanks to @BerSecHub for reporting this issue.

CVE-2026-76805 Affected Nuclei Versions

1 component(s)
Fixed Versions:
3.10.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/projectdiscovery/nuclei/v3
Go
≥ 3.0.0
< 3.10.0
3.10.0

References

Frequently Asked Questions

What is CVE-2026-76805?
CVE-2026-76805 is a security vulnerability in Nuclei involving Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Nuclei versions are affected?
Affected versions include releases prior to 3.10.0 across affected packages: github.com/projectdiscovery/nuclei/v3.
What version fixes CVE-2026-76805?
Upgrading to 3.10.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/projectdiscovery/nuclei/v3 affected?
Yes, github.com/projectdiscovery/nuclei/v3 is affected in releases prior to 3.10.0. Upgrade your dependency to 3.10.0 or later.
What is the CVSS score of CVE-2026-76805?
CVE-2026-76805 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-76805?
CVE-2026-76805 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for CVE-2026-76805?
Run the dependency tree command: 'inspect dependencies for github.com/projectdiscovery/nuclei/v3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jpvm-9frm-hjcq",
  "modified" : "2026-09-22T20:37:24Z",
  "published" : "2026-09-22T20:37:24Z",
  "aliases" : [ "CVE-2026-76805" ],
  "summary" : "Nuclei: Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode",
  "details" : "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.\n\nThis is an incomplete fix for [CVE-2026-41645](https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jm34-66cf-qpvr) / 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.\n\n**Affected Component**\n\nThe 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.\n\n**Description**\n\nIn DAST/fuzz mode, payload evaluation previously ran expression substitution more than once on the same value. Response-derived content captured by an `internal: true` extractor in a prior protocol step could flow into a fuzz payload and be reinterpreted as DSL/helper syntax on a subsequent pass.\n\nWhen `-env-vars` (`-ev`) is enabled, environment variables are merged into the template variable map. A malicious target can return response data containing expressions like `{{env_var_name}}` which, when reused in a subsequent fuzz step, resolve to actual environment variable values. This can expose sensitive host data such as API keys, credentials, and tokens.\n\nWithout `-ev` enabled (the default), response-derived data may still cause other DSL helpers to run, but that behavior is not treated as a security issue and has no meaningful security impact beyond unexpected behavior.\n\n> [!NOTE]\nThe `-env-vars` / `-ev` option is off by default. Users who have not explicitly enabled it are not affected by this vulnerability.\n\n**Affected Users**\n\n- **CLI users** running `nuclei -dast` (or fuzzing) with multi-step templates that chain an internal extractor into a subsequent fuzz step against untrusted targets, with the `-ev` flag enabled.\n- **SDK users** who integrate Nuclei with the fuzz pipeline enabled, `EnvironmentVariables` set to `true`, and scan targets that are not fully trusted.\n\n**Patches**\n\n- The vulnerability is fixed in Nuclei v3.10.0. Upgrading is strongly recommended.\n- Fix reference: https://github.com/projectdiscovery/nuclei/pull/7499\n- Related original fix: https://github.com/projectdiscovery/nuclei/pull/7221, https://github.com/projectdiscovery/nuclei/pull/7321\n\n**Mitigation**\n\nUpgrade to Nuclei v3.10.0, where template-authored text is rendered once through a shared rendering boundary and runtime values from responses, extractors, and constants remain opaque data.\n\nIf you have `-ev` enabled, disable it when scanning untrusted targets to avoid environment variable disclosure.\n\n**Workarounds**\n\nIf upgrading is not an option, ensure `-env-vars` / `-ev` is not enabled when running DAST/fuzz scans with multi-step templates against untrusted targets.\n\n**Acknowledgments**\n\nThanks to @BerSecHub for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/projectdiscovery/nuclei/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.10.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-jpvm-9frm-hjcq"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-76805"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/pull/7499"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/commit/ccbfb12bd01447ba25f6e755dfb2bee677736da6"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/projectdiscovery/nuclei"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projectdiscovery/nuclei/releases/tag/v3.10.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-22T20:37:24Z",
    "nvd_published_at" : "2026-09-22T17:17:25Z"
  }
}