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 products
miguelgrinberg: flask-httpauth
References4
- github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GH… MitigationVendor Advisory
- github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d… Patch
- github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1 ProductRelease Notes
- lists.debian.org/debian-lts-announce/2026/05/msg00049.html
Metrics
- CVSS 3.1
-
8.2
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N - EPSS — exploit probability
- 0% percentile: 27 · as of 12 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.