Flask Security Too
Approved changes feed: RSS · Atom
cpe:2.3:a:pallets-eco:flask-security-too:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Pallets Eco (a1fc8258-891e-553c-b42b-31bd8e418284) |
|---|---|
| Product | Flask Security Too (202c42e6-462c-5abd-8288-2a0a7a0653a4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-46715 |
vulnerable | 2026-07-29 00:54:59.184883 |
Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance
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.
Published: 2026-07-20T17:10:27.014Z
Updated: 2026-07-20T18:43:54.970Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.