Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p44q-vqpr-4xmg | Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client |
Thu, 16 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | NVD-CWE-noinfo | |
| CPEs | cpe:2.3:a:miguelgrinberg:flask-httpauth:*:*:*:*:*:python:*:* |
Thu, 02 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Miguelgrinberg
Miguelgrinberg flask-httpauth |
|
| Vendors & Products |
Miguelgrinberg
Miguelgrinberg flask-httpauth |
Wed, 01 Apr 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-02T16:24:04.160Z
Reserved: 2026-03-30T16:03:31.048Z
Link: CVE-2026-34531
No data.
Status : Analyzed
Published: 2026-04-01T21:17:01.147
Modified: 2026-04-16T16:21:05.147
Link: CVE-2026-34531
No data.
OpenCVE Enrichment
Updated: 2026-04-17T10:00:03Z
Github GHSA