Advisory record · GHSA-p44q-vqpr-4xmg

Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client

CVSS 6.5 MediumEPSS 0.0034 · 28th percentile

Published by the GitHub Advisory Database at 31 Mar 2026, 23:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
flask-httpauthPyPI<4.8.14.8.1
Identifiers
GHSA-p44q-vqpr-4xmg · CVE-2026-34531 · PYSEC-2026-2152
Weakness (CWE)
CWE-287
Published
31 Mar 2026
Updated
13 Jul 2026

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.

Written 6 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 15:04 UTC First seen by agentprime
  2. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.