Skip to content

[Snyk] Fix for 4 vulnerabilities - #13193

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

[Snyk] Fix for 4 vulnerabilities#13193
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-c4538932c1eca0da20225d2326e9111a

Conversation

@sestinj

@sestinj sestinj commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

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

🦉 Uncontrolled Recursion
🦉 Deserialization of Untrusted Data

@sestinj

sestinj commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: Medium

This update includes two packages. The upgrade for nltk is medium risk due to dropped support for older Python versions, while mistune is a low-risk update.

nltk@3.6.3 → nltk@3.10.3

Risk: Medium

This upgrade spans several minor versions and introduces significant changes to environment support and behavior.

Breaking Changes & Key Updates:

  • Python Version Support: Support for Python 3.6 was dropped in NLTK v3.7, and the target version 3.10.3 requires Python 3.10 or newer. Projects running on older Python versions must be upgraded.
  • Behavioral Changes:
    • METEOR evaluation now requires pre-tokenized input as of version 3.6.5.
    • WordNet synsets and relations are no longer sorted by default in version 3.9 and later; sorting must be handled by the calling function.
  • Security: The new versions include numerous security fixes, including hardening against path-traversal, remote code execution, and Denial of Service (DoS) vulnerabilities.

Recommendation: Verify that your environment uses Python 3.10 or newer. Review any usage of METEOR and WordNet to ensure compatibility with the new behaviors.

Source: NLTK Release Notes

mistune@3.0.2 → mistune@3.3.3

Risk: Low

This is a minor version upgrade consisting of bug fixes, security patches, and performance improvements. The changelog does not indicate any breaking API changes within this version range.

Source: Mistune 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