<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T18:30:58.313037+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-76804</id>
    <title>fkie_cve-2026-76804</title>
    <updated>2026-10-04T18:30:58.314907+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Nuclei is a vulnerability scanner built on a simple YAML-based DSL. From 3.0.0 until 3.10.0, the workflow template loading path does not enforce the -file capability gate when resolving file: protocol templates referenced by a workflow. An untrusted unsigned workflow can therefore load a file-protocol template and read local files from the scanner host even when the operator has not enabled file templates. The issue affects CLI users running workflows with -w and SDK integrations that accept end-user workflows while relying on the default file-access restriction. This issue is fixed in version 3.10.0.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-76804"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-qgw5-7j4f-fg97</id>
    <title>GHSA-qgw5-7j4f-fg97 — Nuclei: Local File Read via Workflow File-Protocol Gate Bypass</title>
    <updated>2026-10-04T18:30:58.315022+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/projectdiscovery/nuclei/v3</p>
<p>A vulnerability in Nuclei's workflow template loader allows `file:` protocol templates to execute without the `-file` flag, bypassing a security gate that is meant to prevent local file reads on the scanner host.</p>
<p>**Affected Component**</p>
<p>The issue is in the workflow template loading path. The main template loader enforces the `-file` gate for file-protocol templates, but the workflow loader did not apply the same check when resolving templates referenced by a workflow.</p>
<p>**Description**</p>
<p>Nuclei disables file-protocol templates by default because they read local files from the host running the scanner. Operators must explicitly enable them with the `-file` flag. When a workflow references a file-protocol template, the workflow loader accepted and executed that template without verifying that `-file` was enabled.</p>
<p>Because workflows run unsigned by default, an untrusted workflow could load and execute a file-protocol template and read local files from the scan target path, even though the operator had not enabled file templates.</p>
<p>&gt; [!NOTE]
File-protocol templates are disabled by default. This issue only affects users who run workflows from untrusted sources without having explicitly enabled `-file`.</p>
<p>**Affected Users**</p>
<p>- **CLI users** running workflows (`-w`) that reference file-protocol templates from untrusted or third-party sources.
- **SDK users** who integrate Nuclei into platforms where end users can supply workflow files and rely on the default `-file` restriction to blo…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-qgw5-7j4f-fg97"/>
  </entry>
</feed>
