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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vqpr-4xmg Mitigation, Vendor Advisory
- https://github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd944f642079e1dcf9ee Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.2 · miguelgrinbergNVD modified 2026-10-26 22:10
Affected (CPE criteria) 1
cpe:2.3:a:miguelgrinberg:flask-httpauth:*:*:*:*:*:python:*:*
References 4
- 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