Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-71513: NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only th

47
This month
HIGH 8.8UPGRADE

CVE-2026-71513 is a high-severity flaw (CVSS 8.8) affecting nltk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only the pickle module string and not the global name, allowing attackers to resolve dotted names by attribute traversal to callables outside the allowlisted namespace. Attackers can craft untrusted transition-parser models that execute arbitrary commands when TransitionParser.parse loads the model through allowlisted_pickle_load.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance1.1% (top 35%)
CISA exploited listNo
WeaknessCWE-502
Published2026-08-22
Last modified2026-10-14
Publisher (CNA): VulnCheck · Vendor: nltk

Share: LinkedIn · X · Reddit

Last updated 2026-10-14 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nltk nltk UPGRADE
Affected: < 3.10.3
Fixed in: 3.10.3
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy nltk || rpm -q nltk || nltk --version
2. UPGRADE to 3.10.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nltk
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nltk
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-71513?

nltk: upgrade to 3.10.3. Exact commands for each OS are on this page.

Is CVE-2026-71513 being exploited?

CVE-2026-71513 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-71513 affect?

CVE-2026-71513 affects nltk. Severity is high (CVSS 8.8). NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only the pickle module string and not the global name, allowing attackers to resolve dotted names by attribute traversal to callables out

How urgent is CVE-2026-71513?

Priority 47/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.