CVE-2026-34531

Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client

State
Published
Severity
6.5 Medium
Published
Apr 1, 2026
Updated
May 28, 2026
Reserved
Mar 30, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.16.5 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:NGitHub_M

Weaknesses

Affected Products

ProductVersions
Flask-HTTPAuthmiguelgrinberg
  • < 4.8.1Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.