CVE-2026-34531 PUBLISHED

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

Assigner: GitHub_M
Reserved: 30.03.2026 Published: 01.04.2026 Updated: 01.04.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
CVSS Score: 6.5

Product Status

Vendor miguelgrinberg
Product Flask-HTTPAuth
Versions
  • Version < 4.8.1 is affected

References

Problem Types

  • CWE-287: Improper Authentication CWE