eduMFA insufficient session expiration in Passkey challenges

Severity: high · CVSS 8.7 · Published 2026-05-18

eduMFA is a multi-factor authentication solution. In versions prior to 2.9.1, the system fails to properly expire authentication challenges used for Passkey and WebAuthn logins. This could allow an attacker to reuse old authentication data to bypass security measures and gain unauthorized access to user accounts.

Technologies: edumfa (PyPI). Vendors: PyPI.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
High severity, with a CVSS score of 8.7, published 18 May 2026.
Which products and versions are affected?
edumfa (PyPI) < 2.9.1.
Is there a fix for This vulnerability?
A patch was published on 2026-05-18: Fix released in version 2.9.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?
It is attacked over the network, in a software library.
Am I affected?
Check whether you run edumfa (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in eduMFA versions prior to 2.9.1 stems from insufficient session expiration (CWE-613) and improper authentication (CWE-287) within the userless Passkey/WebAuthn implementation. Specifically, authentication challenges lack an expiration flag or validity information, allowing them to be replayed indefinitely. A remote attacker can exploit this by capturing and reusing a valid challenge response to authenticate without possessing the original hardware token or passkey at the time of login. The issue is resolved in version 2.9.1 by incorporating validity metadata into the challenges.

Affected products

  • eduMFA eduMFA < 2.9.1

Timeline

  • 2026-05-11: disclosed: Initial disclosure by researcher
  • 2026-05-18: advisory: GitHub Advisory published
  • 2026-05-18: patched: Fix released in version 2.9.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.