# GHSA-j5rm-v3vh-vx94: eduMFA Passkeys: missing expiration flag may allow replay attacks and reuse of old challenges

> Attackers can replay expired WebAuthn challenges to bypass authentication and take over accounts in eduMFA.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 May 2026

## What is GHSA-j5rm-v3vh-vx94?

GHSA-j5rm-v3vh-vx94 is a vulnerability in edumfa, published on 18 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

## Which versions are affected by GHSA-j5rm-v3vh-vx94?

2 open source packages ship an affected version, including edumfa.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `edumfa` | PyPI | All versions | 2.9.1 |
| `edumfa` | PyPI | All versions | 2.9.1 |

## How do I fix GHSA-j5rm-v3vh-vx94?

Upgrade edumfa to 2.9.1 or later.

## Is GHSA-j5rm-v3vh-vx94 being exploited?

There is no known exploitation of GHSA-j5rm-v3vh-vx94 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j5rm-v3vh-vx94 and fix it if it is affected.

What it is: GHSA-j5rm-v3vh-vx94 is a vulnerability in edumfa, published on 18 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-j5rm-v3vh-vx94 in the wild and no public exploit code.

Affected packages and fixed versions:
- edumfa (PyPI): affected all versions; fixed in 2.9.1
- edumfa (PyPI): affected all versions; fixed in 2.9.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-j5rm-v3vh-vx94/ (Markdown: https://insights.sbomify.com/GHSA-j5rm-v3vh-vx94/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j5rm-v3vh-vx94

---
From sbomify Insights: https://insights.sbomify.com/GHSA-j5rm-v3vh-vx94/
Summaries are generated and may contain mistakes; the official description above is the record.