● High · CVSS 8.6

How to Fix CVE-2026-0847: Path traversal in nltk/nltk

Q: What is the CVSS score for CVE-2026-0847?

8.6 (High). Vector: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`.

Q: Where is the official advisory for CVE-2026-0847?

The vendor advisory is at [https://huntr.com/bounties/fc69914f-36a9-4c18-8503-10013b39f966](https://huntr.com/bounties/fc69914f-36a9-4c18-8503-10013b39f966). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-0847.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-0847 is a path traversal in nltk nltk/nltk. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	8.6 (High)
Actively exploited?	No public listing in CISA KEV
Affected	nltk/nltk unspecified to <=latest
Fixed in	See vendor advisory
Type (CWE)	CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-0847?

A vulnerability in NLTK versions up to and including 3.9.2 allows arbitrary file read via path traversal in multiple CorpusReader classes, including WordListCorpusReader, TaggedCorpusReader, and BracketParseCorpusReader. These classes fail to properly sanitize or validate file paths, enabling attackers to traverse directories and access sensitive files on the server. This issue is particularly critical in scenarios where user-controlled file inputs are processed, such as in machine learning APIs, chatbots, or NLP pipelines. Exploitation of this vulnerability can lead to unauthorized access to sensitive files, including system files, SSH private keys, and API tokens, and may potentially escalate to remote code execution when combined with other vulnerabilities. The CVSS base score is 8.6 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://huntr.com/bounties/fc69914f-36a9-4c18-8503-10013b39f966.

Am I affected?

Check the version of nltk/nltk you are running and compare it against the Affected row above (nltk/nltk unspecified to <=latest). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s nltk-nltk 2>/dev/null | grep -i ^Version
rpm -q nltk-nltk 2>/dev/null
command -v nltk-nltk >/dev/null && nltk-nltk --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*nltk/nltk*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "nltk/nltk" 2>$null

How to fix CVE-2026-0847

Upgrade nltk/nltk to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade nltk-nltk
dpkg -s nltk-nltk | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh nltk-nltk -y
# or for older releases:
sudo yum update nltk-nltk -y
rpm -q nltk-nltk

SUSE / openSUSE


sudo zypper refresh
sudo zypper update nltk-nltk
rpm -q nltk-nltk

Node.js / npm


# Update the affected package in your project
npm install nltk/nltk@latest
npm ls nltk/nltk
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-0847 affecting nltk/nltk
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-0847-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*nltk/nltk*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\nltk-nltk-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\nltk/nltk" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "nltk/nltk" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "nltk/nltk"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-0847 affecting nltk/nltk
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-0847-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s nltk-nltk 2>/dev/null | grep -i ^Version || echo "nltk-nltk not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q nltk-nltk || echo "nltk-nltk not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-0847-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/nltk-nltk /etc/nltk-nltk.d /etc/nltk-nltk.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y nltk-nltk
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y nltk-nltk
elif command -v yum >/dev/null; then
    yum update -y nltk-nltk
elif command -v zypper >/dev/null; then
    zypper --non-interactive update nltk-nltk
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s nltk-nltk 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q nltk-nltk
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-0847" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-0847"

Disable the affected service (Linux)


sudo systemctl stop nltk-nltk 2>/dev/null || true
sudo systemctl disable nltk-nltk 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s nltk-nltk 2>/dev/null | grep -i ^Version
rpm -q nltk-nltk 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*nltk/nltk*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-24870: Information Disclosure in ixray-1.6-stcop — Information Disclosure in ixray-1.6-stcop
How to Fix CVE-2026-39397: CWE-862: Missing Authorization in payload-puck — CWE-862: Missing Authorization in payload-puck
How to Fix CVE-2026-45186: Inefficient Algorithmic Complexity in libexpat , Inefficient Algorithmic Complexity in libexpat
How to Fix CVE-2026-1130: SQL Injection in KSOA , SQL Injection in KSOA
How to Fix CVE-2026-5406: CWE-674: Uncontrolled Recursion in Wireshark , CWE-674: Uncontrolled Recursion in Wireshark

Is CVE-2026-0847 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-0847?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-0847?

8.6 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L.

Where is the official advisory for CVE-2026-0847?

The vendor advisory is at https://huntr.com/bounties/fc69914f-36a9-4c18-8503-10013b39f966. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-0847.

References

Official vendor advisory: https://huntr.com/bounties/fc69914f-36a9-4c18-8503-10013b39f966
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0847
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*