{"answers":{"affected":"3 open source packages ship an affected version, including flask-security-too and Flask-Security-Too.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46715 exists.","fix":"Upgrade flask-security-too to 5.8.1 or later.","what":"CVE-2026-46715 is a medium-severity authentication bypass vulnerability in pallets-eco Flask-Security-Too, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46715 and fix it if it is affected.\n\nWhat it is: CVE-2026-46715 is a medium-severity authentication bypass vulnerability in pallets-eco Flask-Security-Too, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46715 exists.\n\nAffected packages and fixed versions:\n- flask-security-too (PyPI): affected from 5.8.0; fixed in 5.8.1\n- flask-security-too (PyPI): affected from 5.8.0; fixed in 5.8.1\n- Flask-Security-Too (PyPI): affected from 5.8.0; fixed in 5.8.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46715/ (Markdown: https://insights.sbomify.com/CVE-2026-46715/index.md)","id":"CVE-2026-46715","markdown":"https://insights.sbomify.com/CVE-2026-46715/index.md","name":"CVE-2026-46715","record":{"aliases":["GHSA-97r5-pg8x-p63p","PYSEC-2026-2478"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Flask security library","requires_auth":"low_privilege","summary":"Attackers can bypass reauthentication checks by linking their OAuth identity to a victim's stale session, enabling unauthorized account actions.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance","id":"CVE-2026-46715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Nezha Monitoring: RoleMember can run shell on every server (cross-tenant RCE) via POST /api/v1/cron","id":"CVE-2026-46716"},"packages":[{"ecosystem":"PyPI","fixed":["5.8.1"],"introduced":["5.8.0"],"last_affected":[],"package":"Flask-Security-Too","purl":null,"source":"GHSA-97r5-pg8x-p63p"},{"ecosystem":"PyPI","fixed":["5.8.1"],"introduced":["5.8.0"],"last_affected":[],"package":"flask-security-too","purl":"pkg:pypi/flask-security-too","source":"GHSA-97r5-pg8x-p63p"},{"ecosystem":"PyPI","fixed":["5.8.1"],"introduced":["5.8.0"],"last_affected":[],"package":"flask-security-too","purl":"pkg:pypi/flask-security-too","source":"PYSEC-2026-2478"}],"prev":{"headline":"Misskey: Denial of Service via Uncontrolled Recursion in Theme Compilation","id":"CVE-2026-46714"},"products":["Flask-Security-Too"],"published":"2026-07-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["pallets-eco"]},"summary":"Attackers can bypass reauthentication checks by linking their OAuth identity to a victim's stale session, enabling unauthorized account actions.","url":"https://insights.sbomify.com/CVE-2026-46715/"}