Skip to content

[Snyk] Security upgrade nltk from 3.6.3 to 3.9.3 - #13032

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

[Snyk] Security upgrade nltk from 3.6.3 to 3.9.3#13032
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-e9d8adfb70545de896b88c276950a21a

Conversation

@sestinj

@sestinj sestinj commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 1 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 murmurhash, which is not installed.
thinc 8.0.17 requires preshed, which is not installed.
thinc 8.0.17 requires cymem, which is not installed.
spacy 3.1.2 requires preshed, which is not installed.
spacy 3.1.2 requires murmurhash, which is not installed.
spacy 3.1.2 requires cymem, 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:

🦉 Eval Injection

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-NLTK-18313041
@sestinj

sestinj commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: Medium

This upgrade for NLTK from version 3.6.3 to 3.9.3 introduces several changes, including dropped support for older Python versions and a behavioral change in WordNet.

Key Changes:

  • Python Version Support: Support for Python 3.6 was dropped in NLTK 3.7, and support for Python 3.8 was dropped in 3.9.2. The target version 3.9.3 requires Python 3.10 or newer.
  • WordNet Sorting: As of version 3.9, WordNet synsets and relations are no longer sorted by default. Code that relies on a specific sorted order from WordNet functions may need to be updated to explicitly sort the results.
  • Security Fix / Model Packaging: To address CVE-2024-39705, version 3.9 replaced pickled models (like punkt and various taggers) with a new pickle-free format. This is noted as a breaking change in the official changelog and may require users to update their downloaded NLTK data packages.

Recommendation:
Verify that your environment is running Python 3.10 or a newer version. Review any code that uses WordNet to ensure that the change in default sorting does not affect its behavior. It is also advisable to redownload NLTK data packages to ensure you have the new, safer model formats.

Source: NLTK Release Notes, NLTK 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