CVE-2025-47278

NameCVE-2025-47278
DescriptionFlask 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.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs1105794

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
flask (PTS)bullseye (security), bullseye1.1.2-2+deb11u1fixed
bookworm2.2.2-3fixed
sid, trixie3.1.1-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
flasksourcebullseye(not affected)
flasksourcebookworm(not affected)
flasksource(unstable)3.1.1-11105794

Notes

[bookworm] - flask <not-affected> (Vulnerable code introduced later)
[bullseye] - flask <not-affected> (Vulnerable code introduced later)
https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g
Fixed by: https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09 (3.1.1)

Search for package or bug name: Reporting problems