CVE-2026-34531: miguelgrinberg Flask-HTTPAuth · Improper Authentication
Affects miguelgrinberg Flask-HTTPAuthSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.8.1 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.8.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Flask-HTTPAuth and flask-httpauth to 4.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| miguelgrinbergFlask-HTTPAuth | Affected
| Fixed in
|
PyPIflask-httpauthpkg:pypi/flask-httpauthOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Flask-HTTPAuth to version 4.8.1 or later, where this issue is patched. Applications should also ensure that no users have empty string tokens assigned. Patch status is confirmed fixed in version 4.8.1.
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.
References
- github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vqpr-4xmg (opens in a new tab)
- github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd944f642079e1dcf9ee (opens in a new tab)
- github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2026/05/msg00049.html (opens in a new tab)