Flask-Security-Too allows users to add security features to their Flask applicationa. Version 5.8.0's OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account that belongs to a different user. If an attacker can operate an already-authenticated but stale victim session, they can complete OAuth verification using their own OAuth identity. The victim session is then treated as recently reauthenticated, allowing freshness-protected account actions to proceed. Version 5.8.1 contains a fix for this issue.
CVE-2026-46715
MEDIUMPre-NVD 5.35.3—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 20.1%
- KEV
- Not listed
Published
May 22, 2026
Last Modified
July 20, 2026
Advisory Details (2)
Auto-updated Jul 20, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available
Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance · Advisory · pallets-eco/flask-security · GitHub
https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x-p63pgithub_commit Patch Available
commit 8e69f3a94a46 (pallets-eco/flask-security)
Patch available: pallets-eco/flask-security 5.8.1 (contains commit 8e69f3a94a46)
https://github.com/pallets-eco/flask-security/commit/8e69f3a94a463c0e8ddc46e31743717559fd8d48Vendor Advisories for CVE-2026-46715(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| flask-security-too | 5.8.0 | 5.8.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:58 UTCEG score recompute▲ 5.30
- 2026-07-20 17:57 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-24 06:09 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-46715?
CVE-2026-46715 is a medium vulnerability published on May 22, 2026. Flask-Security-Too allows users to add security features to their Flask applicationa. Version 5.8.0's OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account that belongs to a different user. If an attacker can operate an already-authenticated but stale victim…
When was CVE-2026-46715 disclosed?
CVE-2026-46715 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46715 actively exploited?
CVE-2026-46715 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46715?
CVE-2026-46715 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-46715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46715, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46715
Is Your Infrastructure Affected by CVE-2026-46715?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.