All reports
Low

Flask uses fallback key instead of current signing key

Affected versions

Version ranges need review.

PyPIflask
Affected versions
>=3.1.0 <3.1.1
Fixed version
3.1.1
PyPIflask
Affected versions
= 3.1.0
Fixed version
3.1.1

Exploitation

CVE-2025-47278

Probability of exploitation in the next 30 days: 0.19%

FIRST EPSS · 2026-11-20

Description

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.

Links

Credits

  • jayaddison
  • Brax94