<?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>Fri, 02 Oct 2026 10:08:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-373216</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-373216</link>
      <description>EUVD-2026-373216</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-373216</guid>
    </item>
    <item>
      <title>fkie_cve-2026-94185</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-94185</link>
      <description>&lt;p&gt;nvm resolves a requested version or alias by treating it as a filename under $NVM_DIR/alias. Before 0.40.8, nvm_alias() concatenated the requested name onto that directory and read the result with no containment check, so a name containing a `..` component escaped the alias directory; under the default layout an alias such as `../../.npmrc` resolves to a file in the user&amp;#39;s home directory. nvm_print_alias_file() then emits every non-comment, non-empty line of whatever was opened. A version string taken from an untrusted .nvmrc reaches this path, so a developer who runs `nvm use`, `nvm install`, or `nvm which` inside an attacker-supplied repository discloses the first non-comment line of an arbitrary file readable by that user, in the resulting &amp;#34;is not yet installed&amp;#34; error message. A user-supplied `nvm alias &amp;lt;traversing-name&amp;gt;` discloses every non-comment line of the target file. There is no integrity or availability impact, and no command execution on this path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nvm resolves a requested version or alias by treating it as a filename under $NVM_DIR/alias. Before 0.40.8, nvm_alias() concatenated the requested name onto that directory and read the result with no containment check, so a name containing a `..` component escaped the alias directory; under the default layout an alias such as `../../.npmrc` resolves to a file in the user&amp;#39;s home directory. nvm_print_alias_file() then emits every non-comment, non-empty line of whatever was opened. A version string taken from an untrusted .nvmrc reaches this path, so a developer who runs `nvm use`, `nvm install`, or `nvm which` inside an attacker-supplied repository discloses the first non-comment line of an arbitrary file readable by that user, in the resulting &amp;#34;is not yet installed&amp;#34; error message. A user-supplied `nvm alias &amp;lt;traversing-name&amp;gt;` discloses every non-comment line of the target file. There is no integrity or availability impact, and no command execution on this path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-94185</guid>
    </item>
  </channel>
</rss>
