nltk 3.10.2
PkgFire would stop this release from installing.·Checked 17 hours ago·Published 5 August 2026
Why
-
blockVulnerability
PYSEC-2026-3735 (fixed in 3.10.3)
-
blockVulnerability
PYSEC-2026-3749 (fixed in 3.10.3)
-
blockVulnerability
NLTK: JVM argument injection bypass via per-call options in the NLTK Stanford wrappers (incomplete fix of CVE-2026-12841) (fixed in 3.10.3)
-
blockVulnerability
NLTK: Allowlisted pickle loaders still permit code execution in current source (fixed in 3.10.3)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- None, and no earlier version had any
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.