CVEvulnerability
CVE-2026-34531
8.2 HIGH
Official page ↗
- Status
- Modified
- Published
- 2026-04-01
- Last modified
- 2026-10-26
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 6.5 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
- CVSS 3.1 ([email protected])
- 8.2 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
- Weaknesses
- CWE-287
Description
Flask-HTTPAuth provides Basic, Digest and Token HTTP authentication for Flask routes. Prior to version 4.8.1, in a situation where the client makes a request to a token protected resource without passing a token, or passing an empty token, Flask-HTTPAuth would invoke the application's token verification callback function with the token argument set to an empty string. If the application had any users in its database with an empty string set as their token, then it could potentially authenticate the client request against any of those users. This issue has been patched in version 4.8.1.
Affected configurations
• miguelgrinberg flask-httpauth (< 4.8.1)
Related
Weakness · CWE (1)
- CWE-287 Improper Authentication weakness
References
- https://github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1 Product, Release Notes
- https://github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vqpr-4xmg Mitigation, Vendor Advisory
- https://github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd944f642079e1dcf9ee Patch
- https://lists.debian.org/debian-lts-announce/2026/05/msg00049.html lists.debian.org