Skip to content

[Snyk] Security upgrade nltk from 3.6.3 to 3.10.3 - #13188

Open
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-3a32dc0802ca59c6e081fa36c7a30b16
Open

[Snyk] Security upgrade nltk from 3.6.3 to 3.10.3#13188
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-3a32dc0802ca59c6e081fa36c7a30b16

Conversation

@sestinj

@sestinj sestinj commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 6 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • manual-testing-sandbox/requirements.txt
⚠️ Warning
typer 0.3.2 has requirement click<7.2.0,>=7.1.1, but you have click 8.1.8.
thinc 8.0.17 requires preshed, which is not installed.
thinc 8.0.17 requires murmurhash, which is not installed.
thinc 8.0.17 requires cymem, which is not installed.
spacy 3.1.2 requires murmurhash, which is not installed.
spacy 3.1.2 requires cymem, which is not installed.
spacy 3.1.2 requires preshed, which is not installed.
qtconsole 5.4.4 requires pyzmq, which is not installed.
notebook 6.5.7 requires pyzmq, which is not installed.
jupyter-server 1.24.0 requires pyzmq, which is not installed.
jupyter-console 6.6.3 requires pyzmq, which is not installed.
jupyter-client 7.4.9 requires pyzmq, which is not installed.
ipykernel 6.16.2 requires pyzmq, which is not installed.
exceptiongroup 1.3.1 has requirement typing-extensions>=4.6.0; python_version < "3.13", but you have typing-extensions 3.10.0.2.

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Directory Traversal

@sestinj
sestinj requested a review from a team as a code owner August 24, 2026 09:25
@sestinj

sestinj commented Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: Medium

This upgrade spans several minor versions and introduces environment and behavioral changes that require verification.

Key Changes:

  • Python Version Requirement: The target version nltk@3.10.3 requires Python 3.10 or newer. [7] Support for Python versions 3.6, 3.7, and 3.8 was dropped in intermediate releases. [1]
  • WordNet Sorting: As of version 3.9, WordNet synsets and relations are no longer sorted by default. Code that relies on a sorted output must now explicitly sort the results. [2]
  • METEOR Evaluation: Since version 3.6.5, the METEOR evaluation function requires pre-tokenized input, which may require changes to how it is called. [1]
  • Security Fixes: This upgrade incorporates numerous security patches, including replacing pickled models to resolve CVE-2024-39705, which is noted as a breaking change. [2, 10]

Recommendation:
Ensure your environment uses Python 3.10+. Review any code using WordNet's synset/relation ordering or the METEOR evaluation function to ensure compatibility.

Source: NLTK Release Notes, GitHub ChangeLog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants