eduMFA: Unauthenticated Failcounter Increment on Resolver Tokens via /validate/check

published 2026-05-18 5mo ago modified 2026-05-18 5mo ago

cvss: 6.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### 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.

Patch / fix

fixed in 1

pypi edumfa 2.9.1

Is GHSA-74r7-3mjm-jc5v in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	edumfa	<2.9.1	2.9.1

Classification

Weakness

CWE-20 Improper Input Validation

References

Sources

GitHub Advisory GHSA-74r7-3mjm-jc5v

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.