flask-3.1.0-py3-none-any.whl: 2 vulnerabilities (highest severity is: 4.3)

[mend-bolt-for-github]

Vulnerable Library - flask-3.1.0-py3-none-any.whl

A simple framework for building complex web applications.

Library home page: https://files.pythonhosted.org/packages/af/47/93213ee66ef8fae3b93b3e29206f6b251e65c97bd91d8e1c5596ef15af0a/flask-3.1.0-py3-none-any.whl

Path to dependency file: /Pi-CryptoConnect-Xtreme/requirements.txt

Path to vulnerable library: /Pi-CryptoConnect-Xtreme/requirements.txt

Found in HEAD commit: 2ed3e6d266405677eb45c15a472c288b604a1cad

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (flask version)	Remediation Possible**
CVE-2026-27205	Medium	4.3	flask-3.1.0-py3-none-any.whl	Direct	flask - 3.1.3	❌
CVE-2025-47278	Low	2.3	flask-3.1.0-py3-none-any.whl	Direct	3.1.1	❌

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-27205

Vulnerable Library - flask-3.1.0-py3-none-any.whl

A simple framework for building complex web applications.

Library home page: https://files.pythonhosted.org/packages/af/47/93213ee66ef8fae3b93b3e29206f6b251e65c97bd91d8e1c5596ef15af0a/flask-3.1.0-py3-none-any.whl

Path to dependency file: /Pi-CryptoConnect-Xtreme/requirements.txt

Path to vulnerable library: /Pi-CryptoConnect-Xtreme/requirements.txt

Dependency Hierarchy:

• ❌ flask-3.1.0-py3-none-any.whl (Vulnerable Library)

Found in HEAD commit: 2ed3e6d266405677eb45c15a472c288b604a1cad

Found in base branch: main

Vulnerability Details

Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Python in operator were overlooked. The severity and risk depend on the application being hosted behind a caching proxy that doesn't ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.

Publish Date: 2026-02-21

URL: CVE-2026-27205

CVSS 3 Score Details (4.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-68rp-wp8r-4726

Release Date: 2026-02-20

Fix Resolution: flask - 3.1.3

Step up your Open Source Security Game with Mend here

CVE-2025-47278

Vulnerable Library - flask-3.1.0-py3-none-any.whl

A simple framework for building complex web applications.

Library home page: https://files.pythonhosted.org/packages/af/47/93213ee66ef8fae3b93b3e29206f6b251e65c97bd91d8e1c5596ef15af0a/flask-3.1.0-py3-none-any.whl

Path to dependency file: /Pi-CryptoConnect-Xtreme/requirements.txt

Path to vulnerable library: /Pi-CryptoConnect-Xtreme/requirements.txt

Dependency Hierarchy:

• ❌ flask-3.1.0-py3-none-any.whl (Vulnerable Library)

Found in HEAD commit: 2ed3e6d266405677eb45c15a472c288b604a1cad

Found in base branch: main

Vulnerability Details

Flask is a web server gateway interface (WSGI) web application framework. In Flask 3.1.0, the way fallback key configuration was handled resulted in the last fallback key being used for signing, rather than the current signing key. Signing is provided by the "itsdangerous" library. A list of keys can be passed, and it expects the last (top) key in the list to be the most recent key, and uses that for signing. Flask was incorrectly constructing that list in reverse, passing the signing key first. Sites that have opted-in to use key rotation by setting "SECRET_KEY_FALLBACKS" care likely to unexpectedly be signing their sessions with stale keys, and their transition to fresher keys will be impeded. Sessions are still signed, so this would not cause any sort of data integrity loss. Version 3.1.1 contains a patch for the issue.

Publish Date: 2025-05-13

URL: CVE-2025-47278

CVSS 3 Score Details (2.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: Low
  • Privileges Required: High
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-4grg-w6v8-c28g

Release Date: 2025-05-13

Fix Resolution: 3.1.1

Step up your Open Source Security Game with Mend here