Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Miguelgrinberg | Flask-Httpauth | < 4.8.1 |
Related Weaknesses (CWE)
References
- https://github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1ProductRelease Notes
- https://github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vMitigationVendor Advisory
- https://github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd94Patch
FAQ
What is CVE-2026-34531?
CVE-2026-34531 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 pass...
How severe is CVE-2026-34531?
CVE-2026-34531 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-34531?
Check the references section above for vendor advisories and patch information. Affected products include: Miguelgrinberg Flask-Httpauth.