Flask uses fallback key instead of current signing key
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` are 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.
beschreibt (1)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2025-47278US | — | — | ||
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 use… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
- https://github.com/pallets/flaskPACKAGE
- https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09WEB
- https://github.com/pallets/flask/releases/tag/3.1.1WEB
- https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28gWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-47278ADVISORY
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan