CVE-2022-42731: mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to r

This week

HIGH 7.5REMOTEUPGRADE

CVE-2022-42731 is a high-severity flaw (CVSS 7.5) affecting django-mfa2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-294
Published	2022-10-11
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: django-mfa2 project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-11 14:15 UTCPublished CVE record published
2026-06-17 05:05 UTCUpdated Record last modified

django-mfa2 project django-mfa2 UPGRADE

Affected: < 2.5.1 · >= 2.6.0 and < 2.6.1

Fixed in: 2.5.1, 2.6.1

Safe to downgrade to: a release before 2.6.0

1. Check installed version

apt-cache policy django-mfa2 || rpm -q django-mfa2 || django-mfa2 --version

2. UPGRADE to 2.5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-mfa2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-mfa2

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.6.0 (Debian / Ubuntu)

apt-cache madison django-mfa2 sudo apt install django-mfa2=<VERSION_BEFORE_2.6.0> sudo apt-mark hold django-mfa2

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list django-mfa2 sudo dnf downgrade django-mfa2-<VERSION_BEFORE_2.6.0> sudo dnf versionlock add django-mfa2

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-42731?

django-mfa2: upgrade to 2.5.1, 2.6.1. Exact commands for each OS are on this page.

Is CVE-2022-42731 being exploited?

CVE-2022-42731 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-42731 affect?

CVE-2022-42731 affects django-mfa2. Severity is high (CVSS 7.5). mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.

How urgent is CVE-2022-42731?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Django vulnerabilities

References

← Back to latest CVEs