CVE-2026-34224

Description

### Impact An attacker who possesses a valid authentication provider token and a single MFA recovery code or SMS one-time password can create multiple authenticated sessions by sending concurrent login requests via the authData login endpoint. This defeats the single-use guarantee of MFA recovery codes and SMS one-time passwords, allowing session persistence even after the legitimate user revokes detected sessions. ### Patches The fix adds optimistic locking to the authData login path, ensuring that concurrent database updates for the same user fail when the original MFA token array has already been modified by another request. ### Workarounds There is no known workaround.

How to fix CVE-2026-34224

To remediate CVE-2026-34224, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.64 or later
• —upgrade to 9.7.0-alpha.8 or later

Is CVE-2026-34224 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.64, >= 9.0.0, < 9.7.0
• >= 9.0.0, < 9.7.0-alpha.8

CVSS scores

References (7)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-34224
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/commit/661f160edac8daac0486bc94413cf9652876ab92
• WEBgithub.com/parse-community/parse-server/commit/e7efbebba398ce6abe5b6b6fb9829c6ebe310fbf