GHSA-j5rm-v3vh-vx94
eduMFA Passkeys: missing expiration flag may allow replay attacks and reuse of old challenges
Blast Radius
edumfaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
In eduMFA < 2.9.1 userless Passkey/WebAuthn challenges might be replayed and do not expire
Patches
Fixed in eduMFA >= 2.9.1 by adding validity information to the userless challenges.
Workarounds
No known workarounds besides disabling userless login altogether.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | edumfa | all versions | 2.9.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for edumfa. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update edumfa to 2.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j5rm-v3vh-vx94 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j5rm-v3vh-vx94 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-j5rm-v3vh-vx94. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j5rm-v3vh-vx94 in your dependencies?
O3 detects GHSA-j5rm-v3vh-vx94 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.