CVE-2025-47278
May 13, 2025
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.
Affected Packages
flask (CONDA):
Affected version(s) =3.1.0 <3.1.1Fix Suggestion:
Update to version 3.1.1https://github.com/pallets/flask.git (GITHUB):
Affected version(s) =3.1.0 <3.1.1Fix Suggestion:
Update to version 3.1.1flask (PYTHON):
Affected version(s) =3.1.0 <3.1.1Fix Suggestion:
Update to version 3.1.1Related Resources (5)
Do you need more information?
Contact UsCVSS v4
Base Score:
1.8
Attack Vector
LOCAL
Attack Complexity
LOW
Attack Requirements
PRESENT
Privileges Required
HIGH
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
NONE
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
2.3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Weakness Type (CWE)
Function Call With Incorrect Order of Arguments
EPSS
Base Score:
0.03