# Flask uses fallback key instead of current signing key

Advisory record · `GHSA-4grg-w6v8-c28g`

- **Identifiers:** `GHSA-4grg-w6v8-c28g` · `CVE-2025-47278` · `PYSEC-2026-1377`
- **State:** Confirmed
- **Severity:** CVSS 1.8 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-683](https://cwe.mitre.org/data/definitions/683.html)
- **Tags:** [CWE-683](https://agentprime.io/advisories/tag/cwe-683.md)
- **Published:** 13 May 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2025, 20:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `flask` (PyPI): affected `>=3.1.0, <3.1.1`; fixed in `3.1.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Flask versions 3.1.0 up to, but not including, 3.1.1 are affected. Sites that use key rotation through SECRET_KEY_FALLBACKS sign sessions with a stale fallback key instead of the current signing key, which can stall their move to newer keys. Upgrade to Flask 3.1.1, which is the listed fixed version. The source says sessions remain signed, so no loss of data integrity is expected.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 1.8 Low, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 13 May 2025, 15:01 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g)
- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4grg-w6v8-c28g)

## Sources

- [GitHub Advisory Database: GHSA-4grg-w6v8-c28g](https://github.com/advisories/GHSA-4grg-w6v8-c28g)
- [OSV: GHSA-4grg-w6v8-c28g](https://osv.dev/vulnerability/GHSA-4grg-w6v8-c28g)
- <https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-47278>
- <https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09>
- <https://github.com/pallets/flask>
- <https://github.com/pallets/flask/releases/tag/3.1.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4grg-w6v8-c28g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4grg-w6v8-c28g/>. Everything for agents: <https://agentprime.io/llms.txt>.
