Skip to content

[Snyk] Security upgrade keras from 2.6.0 to 3.12.0#11019

Open
sestinj wants to merge 1 commit intomainfrom
snyk-fix-7180561ba22f39faa90e7b1669a05ff2
Open

[Snyk] Security upgrade keras from 2.6.0 to 3.12.0#11019
sestinj wants to merge 1 commit intomainfrom
snyk-fix-7180561ba22f39faa90e7b1669a05ff2

Conversation

@sestinj
Copy link
Contributor

@sestinj sestinj commented Mar 4, 2026

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 cymem, which is not installed.
thinc 8.0.17 requires preshed, which is not installed.
thinc 8.0.17 requires murmurhash, which is not installed.
spacy 3.1.2 requires cymem, which is not installed.
spacy 3.1.2 requires murmurhash, 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.

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:

🦉 Directory Traversal


Continue Tasks: 🔄 1 running · ✅ 6 no changes — View all


Summary by cubic

Upgrade Keras from 2.6.0 to 3.12.0 in manual-testing-sandbox/requirements.txt to fix security issue SNYK-PYTHON-KERAS-14152002. This removes the vulnerability and moves the sandbox to the supported Keras 3 line.

  • Dependencies

    • keras: 2.6.0 → 3.12.0
  • Migration

    • Keras 3 uses pluggable backends; ensure your backend (TensorFlow/JAX/PyTorch) is installed and set via KERAS_BACKEND if needed.
    • Check for deprecated 2.x APIs in sandbox code and update as required.

Written for commit f42f1a3. Summary will update on new commits.

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-KERAS-14152002
@sestinj sestinj requested a review from a team as a code owner March 4, 2026 09:57
@sestinj sestinj requested review from Patrick-Erichsen and removed request for a team March 4, 2026 09:57
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Mar 4, 2026
@continue
Copy link
Contributor

continue bot commented Mar 4, 2026

Docs Update Review

No documentation updates are needed for this PR.

Reason: This is a Snyk security upgrade affecting only manual-testing-sandbox/requirements.txt—an internal test fixture. The keras version bump (2.6.0 → 3.12.0) has no impact on user-facing functionality, configuration, or documented features.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="manual-testing-sandbox/requirements.txt">

<violation number="1" location="manual-testing-sandbox/requirements.txt:29">
P2: `keras==3.12.0` is incompatible with the existing `tensorflow==2.6.0` pin, so this dependency set is not installable/reliable as-is.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

# Deep Learning
torch==2.6.0
keras==2.6.0
keras==3.12.0
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: keras==3.12.0 is incompatible with the existing tensorflow==2.6.0 pin, so this dependency set is not installable/reliable as-is.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At manual-testing-sandbox/requirements.txt, line 29:

<comment>`keras==3.12.0` is incompatible with the existing `tensorflow==2.6.0` pin, so this dependency set is not installable/reliable as-is.</comment>

<file context>
@@ -26,7 +26,7 @@ spacy==3.1.2
 # Deep Learning
 torch==2.6.0
-keras==2.6.0
+keras==3.12.0
 
 # Image processing
</file context>
Suggested change
keras==3.12.0
keras==2.6.0
Fix with Cubic

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

Labels

size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

2 participants