<?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://vulnerability.circl.lu</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 05:59:54 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13473</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-13473</link>
      <description>bdu:2026-13473</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-13473</guid>
    </item>
    <item>
      <title>BREW-acronym-CVE-2026-62388 — NLTK: Default ENFORCE=False Disables All pathsec Security Controls</title>
      <link>https://vulnerability.circl.lu/vuln/brew-acronym-cve-2026-62388</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: acronym&lt;/p&gt;
&lt;p&gt;NLTK&amp;#39;s pathsec.py security module defaults to ENFORCE=False (line 24), which means all 8 security validation functions only emit RuntimeWarning instead of raising exceptions when violations are detected.&lt;/p&gt;
&lt;p&gt;The pathsec module was introduced as the fix for CVE-2024-39705 (arbitrary code execution via pickle) and CVE-2026-0846 (path traversal). However, with ENFORCE=False as the default:&lt;/p&gt;
&lt;p&gt;1. pathsec.open(&amp;#39;/etc/passwd&amp;#39;) succeeds (reads the file, emits warning)
2. pathsec.validate_network_url(&amp;#39;http://169.254.169.254/...&amp;#39;) succeeds (warning only)
3. pickle.loads() via nltk.data.load() proceeds despite unsafe source (warning only)&lt;/p&gt;
&lt;p&gt;Every security gate follows the same pattern:
```python
ENFORCE = os.environ.get(&amp;#39;NLTK_PATHSEC_ENFORCE&amp;#39;, &amp;#39;&amp;#39;).lower() in (&amp;#39;1&amp;#39;, &amp;#39;true&amp;#39;, &amp;#39;yes&amp;#39;)&lt;/p&gt;
&lt;p&gt;def validate_something(path):
    if is_violation(path):
        if ENFORCE:
            raise SecurityError(&amp;#39;...&amp;#39;)  # Only raised when env var is set
        else:
            warnings.warn(&amp;#39;...&amp;#39;, RuntimeWarning)  # Default: warning only
    # Execution continues regardless
```&lt;/p&gt;
&lt;p&gt;This means the security remediations for CVE-2024-39705 and CVE-2026-0846 are effectively disabled by default. Any user who installed NLTK 3.9.x expecting the security fixes to be active is still vulnerable unless they manually set NLTK_PATHSEC_ENFORCE=1.&lt;/p&gt;
&lt;p&gt;PoC:
```python
import nltk.pathsec
import warnings&lt;/p&gt;
&lt;p&gt;# Show that ENFORCE is False by default
print(f&amp;#39;ENFORCE = {nltk.pathsec.ENFORCE}&amp;#39;)  # False&lt;/p&gt;
&lt;p&gt;# Attempt to read /etc/passwd through path…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: acronym&lt;/p&gt;
&lt;p&gt;NLTK&amp;#39;s pathsec.py security module defaults to ENFORCE=False (line 24), which means all 8 security validation functions only emit RuntimeWarning instead of raising exceptions when violations are detected.&lt;/p&gt;
&lt;p&gt;The pathsec module was introduced as the fix for CVE-2024-39705 (arbitrary code execution via pickle) and CVE-2026-0846 (path traversal). However, with ENFORCE=False as the default:&lt;/p&gt;
&lt;p&gt;1. pathsec.open(&amp;#39;/etc/passwd&amp;#39;) succeeds (reads the file, emits warning)
2. pathsec.validate_network_url(&amp;#39;http://169.254.169.254/...&amp;#39;) succeeds (warning only)
3. pickle.loads() via nltk.data.load() proceeds despite unsafe source (warning only)&lt;/p&gt;
&lt;p&gt;Every security gate follows the same pattern:
```python
ENFORCE = os.environ.get(&amp;#39;NLTK_PATHSEC_ENFORCE&amp;#39;, &amp;#39;&amp;#39;).lower() in (&amp;#39;1&amp;#39;, &amp;#39;true&amp;#39;, &amp;#39;yes&amp;#39;)&lt;/p&gt;
&lt;p&gt;def validate_something(path):
    if is_violation(path):
        if ENFORCE:
            raise SecurityError(&amp;#39;...&amp;#39;)  # Only raised when env var is set
        else:
            warnings.warn(&amp;#39;...&amp;#39;, RuntimeWarning)  # Default: warning only
    # Execution continues regardless
```&lt;/p&gt;
&lt;p&gt;This means the security remediations for CVE-2024-39705 and CVE-2026-0846 are effectively disabled by default. Any user who installed NLTK 3.9.x expecting the security fixes to be active is still vulnerable unless they manually set NLTK_PATHSEC_ENFORCE=1.&lt;/p&gt;
&lt;p&gt;PoC:
```python
import nltk.pathsec
import warnings&lt;/p&gt;
&lt;p&gt;# Show that ENFORCE is False by default
print(f&amp;#39;ENFORCE = {nltk.pathsec.ENFORCE}&amp;#39;)  # False&lt;/p&gt;
&lt;p&gt;# Attempt to read /etc/passwd through path…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-acronym-cve-2026-62388</guid>
    </item>
    <item>
      <title>CVE-2026-62388 — NLTK before 3.10.0 Insecure Default Configuration in pathsec.py</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-62388</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nltk&lt;/p&gt;
&lt;p&gt;NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nltk&lt;/p&gt;
&lt;p&gt;NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-62388</guid>
    </item>
    <item>
      <title>PYSEC-2026-3722</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-3722</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nltk&lt;/p&gt;
&lt;p&gt;NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nltk&lt;/p&gt;
&lt;p&gt;NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-3722</guid>
    </item>
  </channel>
</rss>
