GHSA-74r7-3mjm-jc5v: eduMFA: Unauthenticated Failcounter Increment on Resolver Tokens via /validate/check
Impact If the resolver parameter is passed, but the user does not exist, all failcounters of tokens in that resolver will be increased. Patches This, along with other issues, was fixed in eduMFA v2.9.1. Workarounds Limiting access to /validate/check to client applications (i.e. Shibboleth/FreeRADIUS) using an authorization policy with apikeyrequired or using e.g. the reverse proxy.
Published May 18, 2026
Affected packages
edumfa
- Ecosystem
- PyPI
- Affected
- < 2.9.1
- Fixed in
- 2.9.1
- Check
pip show edumfa
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
If the resolver parameter is passed, but the user does not exist, all failcounters of tokens in that resolver will be increased.
Patches
This, along with other issues, was fixed in eduMFA v2.9.1.
Workarounds
Limiting access to /validate/check to client applications (i.e. Shibboleth/FreeRADIUS) using an authorization policy with api_key_required or using e.g. the reverse proxy.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesGHSA-j5rm-v3vh-vx94
eduMFA Passkeys: missing expiration flag may allow replay attacks and reuse of old challenges
high8.7May 18, 2026GHSA-qq2p-4282-cfc5
eduMFA: Incorrect InnoDB snapshot isolation possibly allows token reusage
high7.1May 18, 2026GHSA-vhmj-5q9r-mm9g
BlastRADIUS also affects eduMFA
medium6.8Jul 17, 2024
