PT-2026-29428 · Unknown · Flask-Httpauth
Npbhatter17
·
Published
2026-03-31
·
Updated
2026-04-13
·
CVE-2026-34531
CVSS v3.1
8.2
High
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N |
Name of the Vulnerable Software and Affected Versions
Flask-HTTPAuth versions prior to 4.8.1
Description
Flask-HTTPAuth, when used with token authentication, could potentially authenticate client requests against any user in the database with an empty string set as their token if the client request does not include a token or includes an empty token. This occurs because the application's token verification callback function is invoked with an empty string as the
token argument. This issue only applies to token authentication and applications that verify tokens by searching for them in a user database. It does not affect Basic or Digest authentication, or tokens verified through cryptographic means.Recommendations
Ensure no user in the user database has their
token set to an empty string. Change the value of those tokens to NULL instead. Alternatively, upgrade to Flask-HTTPAuth version 4.8.1 or later.Fix
Improper Authentication
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Flask-Httpauth