CVE-2026-31875

Description

### Impact When multi-factor authentication (MFA) via TOTP is enabled for a user account, Parse Server generates two single-use recovery codes. These codes are intended as a fallback when the user cannot provide a TOTP token. However, recovery codes are not consumed after use, allowing the same recovery code to be used an unlimited number of times. This defeats the single-use design of recovery codes and weakens the security of MFA-protected accounts. An attacker who obtains a single recovery code can repeatedly authenticate as the affected user without the code ever being invalidated. ### Patches The fix ensures that each recovery code is removed from the stored recovery code list after a successful login. ### Workarounds There is no known workaround. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8 - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.33

How to fix CVE-2026-31875

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

• —upgrade to 8.6.33 or later
• —upgrade to 9.6.0-alpha.7 or later

Is CVE-2026-31875 being exploited?

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

Affected packages (2)

• from 0, < 8.6.33, >= 9.0.0, < 9.6.0
• >= 9.0.0-alpha.1, < 9.6.0-alpha.7

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-31875
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/releases/tag/8.6.33
• WEBgithub.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7