fix vulnerabilty with nltk - #21275
Merged
Merged
Conversation
dosubot
Bot
added
the
size:XS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bumps the nltk minimum version constraint from >3.8.1 to >=3.9.3 to address a critical severity (CVSS 10.0) vulnerability present in nltk < 3.9.3. Updates all uv.lock files across the monorepo to resolve to nltk 3.9.4 (the latest available for Python ≥3.10).
Fixes: nltk CVE (CRITICAL 10.0) — nltk 3.9.1 → 3.9.3 (Transitive via llama-index-core)
Note: A small number of lock files resolve to 3.9.2 under python_full_version < '3.10' markers. This is expected — nltk 3.9.3+ requires Python ≥3.10, and llama-index-core itself requires python >=3.10, so those entries are never installed in practice.