<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 23:41:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72744 — Nuxt before 4.5.1 Information Disclosure via Chrome DevTools</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-72744</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nuxt&lt;/p&gt;
&lt;p&gt;Nuxt versions &amp;gt;= 4.4.7 and &amp;lt; 4.5.1, and &amp;gt;= 3.21.7 and &amp;lt; 3.21.10, contain an information disclosure vulnerability in the development server&amp;#39;s Chrome DevTools workspace endpoint (GET /.well-known/appspecific/com.chrome.devtools.json). The endpoint&amp;#39;s local-request gate (isLocalDevRequest) is header-based and trusts the attacker-supplied Host header rather than the connected peer address. When the dev server is bound to a network-reachable interface (e.g. nuxt dev --host) and experimental.chromeDevtoolsProjectSettings is enabled (the default), an unauthenticated attacker on the LAN can send a request with a spoofed Host header and no browser-specific headers (Sec-Fetch-Site, Origin, Referer) to retrieve the project&amp;#39;s absolute filesystem root path (rootDir) and a persistent per-project workspace UUID. Production builds are unaffected. Fixed in 4.5.1 and 3.21.10.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nuxt&lt;/p&gt;
&lt;p&gt;Nuxt versions &amp;gt;= 4.4.7 and &amp;lt; 4.5.1, and &amp;gt;= 3.21.7 and &amp;lt; 3.21.10, contain an information disclosure vulnerability in the development server&amp;#39;s Chrome DevTools workspace endpoint (GET /.well-known/appspecific/com.chrome.devtools.json). The endpoint&amp;#39;s local-request gate (isLocalDevRequest) is header-based and trusts the attacker-supplied Host header rather than the connected peer address. When the dev server is bound to a network-reachable interface (e.g. nuxt dev --host) and experimental.chromeDevtoolsProjectSettings is enabled (the default), an unauthenticated attacker on the LAN can send a request with a spoofed Host header and no browser-specific headers (Sec-Fetch-Site, Origin, Referer) to retrieve the project&amp;#39;s absolute filesystem root path (rootDir) and a persistent per-project workspace UUID. Production builds are unaffected. Fixed in 4.5.1 and 3.21.10.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-72744</guid>
    </item>
  </channel>
</rss>
