flask-httpauth
Affected
- introduced
0, fixed4.8.1(ecosystem)
Fixed versions
4.8.1
Fix
- Fixed version
4.8.1pip install --upgrade flask-httpauth==4.8.1
Advisory
Also known as: CVE-2026-34531, PYSEC-2026-2152
Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client
Summary
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.
Notes
NULL instead.Remediation
To protect against this issue, developers should make sure that no user in the user database has their token set to an empty string. If there are such users, change the value of those tokens to NULL instead.
Alternatively, developers can upgrade their projects to Flask-HTTPAuth>=4.8.1, which fixes this issue.
Medium Basis: The source's own band: MODERATE
0, fixed 4.8.1 (ecosystem)4.8.1
4.8.1pip install --upgrade flask-httpauth==4.8.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0