CVE-2026-34531
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 3.1
- 8.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N - EPSS
- 0.3% chance of exploitation in the next 30 days; higher than 25% of CVEs (scores of 2026-10-26)
- CWE
- CWE-287
- Published
- Modified
- Record from
- the NVD, synced
Affected
- miguelgrinberg:flask-httpauth
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-p44q-vqpr-4xmg | PyPI | flask-httpauth | <4.8.1 | 4.8.1 |
| PYSEC-2026-2152 | PyPI | flask-httpauth | <4.8.1 | 4.8.1 |
References
- https://github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1
- https://github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vqpr-4xmg
- https://github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd944f642079e1dcf9ee
- https://lists.debian.org/debian-lts-announce/2026/05/msg00049.html