CVE Catalog

CVE-2026-34531

MediumCVSS 6.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.32%

25th percentile - higher than 25% of all known CVEs

Summary

Flask-HTTPAuth prior to version 4.8.1 invokes the token verification callback with an empty string when the client makes a request without a token or with an empty token. If any user in the application database has an empty string as their token, the request could be authenticated as that user.

Risk Assessment

Potential unauthorized authentication of a client as a user with an empty token, leading to bypass of access controls on protected resources.

Recommendation

Update Flask-HTTPAuth to version 4.8.1 or later and ensure no users with empty tokens exist in the database.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS