Flask Httpauth
Approved changes feed: RSS · Atom
cpe:2.3:a:miguelgrinberg:flask-httpauth:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Miguelgrinberg (744d0d02-be87-5608-88c4-dddaa9a9ac90) |
|---|---|
| Product | Flask Httpauth (13afbeb9-d564-5f79-8125-65929a8d7962) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/miguelgrinberg/flask-httpauth |
purl2cpe | 2026-06-01 10:17:54.198280 |
pkg:pypi/flask-httpauth |
purl2cpe | 2026-06-01 10:17:54.198282 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-34531 |
vulnerable | 2026-06-08 07:59:12.670043 |
Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client
MEDIUM (6.5)
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.
Published: 2026-04-01T20:44:10.740Z
Updated: 2026-05-28T17:14:53.255Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.