Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Flask-HTTPAuth versions before 4.8.1 are affected. When a client sends a request to a token-protected resource with no token or an empty token, the library calls the application's token verification callback with an empty string. If the application's user database contains users whose token is stored as an empty string, an attacker can authenticate as one of those users. Upgrade to Flask-HTTPAuth 4.8.1 or later. Alternatively, set any empty-string user tokens to NULL.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 28th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-p44q-vqpr-4xmg
- OSV: GHSA-p44q-vqpr-4xmg
- github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vqpr-4xmg
- nvd.nist.gov/vuln/detail/CVE-2026-34531
- github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd944f642079e1dcf9ee
- github.com/miguelgrinberg/Flask-HTTPAuth
- github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1
- lists.debian.org/debian-lts-announce/2026/05/msg00049.html