[Snyk] Security upgrade python from 3.14.0a1-slim to 3.14.0-slim

[hashim21223445]

Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

• Dockerfile.frontend

We recommend upgrading to python:3.14.0-slim, as this image has only 22 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	CVE-2025-6965 SNYK-DEBIAN12-SQLITE3-10753055	714
	Heap-based Buffer Overflow SNYK-DEBIAN12-GNUTLS28-10690985	614
	Double Free SNYK-DEBIAN12-GNUTLS28-10690987	614
	Improper Certificate Validation SNYK-DEBIAN12-PERL-5489190	614
	Race Condition SNYK-DEBIAN12-SYSTEMD-10264074	514

---

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.

---

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:

🦉 Double Free

[semanticdiff-com]

Review changes with  

[gemini-code-assist]

Summary of Changes

Hello @hashim21223445, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security posture of the application by upgrading the Python base image used in the frontend Dockerfile. By moving from python:3.14.0a1-slim to python:3.14.0-slim, it resolves five known vulnerabilities, including critical and high-severity issues, ensuring the application benefits from the latest security patches and a reduced attack surface.

Highlights

• Security Upgrade: This pull request performs a security upgrade of the Python base image in Dockerfile.frontend to address 5 identified vulnerabilities.
• Base Image Update: The Python base image is updated from python:3.14.0a1-slim to python:3.14.0-slim.
• Vulnerability Resolution: The upgrade fixes a critical vulnerability (CVE-2025-6965 in SQLite3) and several high-severity vulnerabilities related to GnuTLS, Perl, and Systemd.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[Copilot]

Pull Request Overview

This PR upgrades the Python Docker base image from version 3.14.0a1-slim to 3.14.0-slim to address 5 security vulnerabilities identified by Snyk.

• Upgrades Python base image from alpha version to stable release
• Addresses critical and high severity security vulnerabilities in underlying dependencies
• Maintains the same slim image variant for consistent container size

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the Python base image for the frontend service from an alpha version to a stable version. While upgrading from a pre-release is a positive step, using Python 3.14 introduces a significant risk of build failures due to the lack of pre-compiled wheels for key dependencies. It also creates an inconsistency with the backend service, which uses Python 3.11. I've left a comment suggesting alignment of Python versions to a more established one to improve reliability and maintainability.

[gemini-code-assist]

While upgrading to a stable Python version is a good practice, using Python 3.14 here raises a couple of significant concerns:

1. Potential for Build Failures: Using a very recent Python version like 3.14 can be risky as many dependencies may not have pre-compiled wheels available for it. For example, pyarrow, a dependency of streamlit, does not have wheels for Python 3.14 in the locked version. This would force poetry to build it from source, but this Dockerfile lacks the necessary build toolchain (e.g., C++ compiler, CMake), which would likely cause the build to fail.

2. Inconsistent Python Versions: This change sets the frontend to use Python 3.14, while the backend (Dockerfile) uses Python 3.11. Managing different Python versions across services increases maintenance complexity and can lead to subtle inconsistencies.

Considering these points, it would be more reliable and maintainable to use a more established Python version for which dependencies are readily available, such as Python 3.11, to align with the backend.