{"answers":{"affected":"2 open source packages ship an affected version, including edumfa.","exploited":"There is no known exploitation of GHSA-74r7-3mjm-jc5v in the wild and no public exploit code.","fix":"Upgrade edumfa to 2.9.1 or later.","what":"GHSA-74r7-3mjm-jc5v is a denial of service vulnerability in edumfa, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-74r7-3mjm-jc5v and fix it if it is affected.\n\nWhat it is: GHSA-74r7-3mjm-jc5v is a denial of service vulnerability in edumfa, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-74r7-3mjm-jc5v in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- edumfa (PyPI): affected all versions; fixed in 2.9.1\n- edumfa (PyPI): affected all versions; fixed in 2.9.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-74r7-3mjm-jc5v/ (Markdown: https://insights.sbomify.com/GHSA-74r7-3mjm-jc5v/index.md)","id":"GHSA-74r7-3mjm-jc5v","markdown":"https://insights.sbomify.com/GHSA-74r7-3mjm-jc5v/index.md","name":"GHSA-74r7-3mjm-jc5v","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"eduMFA authentication server","requires_auth":"none","summary":"Unauthenticated attackers can lock out all users in a resolver by incrementing failcounters via the validate endpoint, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nIf the resolver parameter is passed, but the user does not exist, all failcounters of tokens in that resolver will be increased.\n\n### Patches\nThis, along with other issues, was fixed in eduMFA v2.9.1.\n\n### Workarounds\nLimiting 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"eduMFA: Unauthenticated Failcounter Increment on Resolver Tokens via /validate/check","id":"GHSA-74r7-3mjm-jc5v","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"edumfa","purl":null,"source":"GHSA-74r7-3mjm-jc5v"},{"ecosystem":"PyPI","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"edumfa","purl":"pkg:pypi/edumfa","source":"GHSA-74r7-3mjm-jc5v"}],"products":null,"published":"2026-05-18","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unauthenticated attackers can lock out all users in a resolver by incrementing failcounters via the validate endpoint, requiring an upgrade to fix.","url":"https://insights.sbomify.com/GHSA-74r7-3mjm-jc5v/"}