Parse Server's MFA recovery codes not consumed after use

TRUNG BÌNH 5.9CVE-2026-31875 · BIT-parse-2026-31875 · GHSA-4hf6-3x24-c9m8 · Công bố 11/03/2026 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2026-31875 là lỗ hổng mức TRUNG BÌNH (CVSS 5.9) ảnh hưởng parse-server (parseplatform), parse-server.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.49%, cao hơn 42.2% các lỗ hổng khác.
Cách xử lý: cập nhật lên 9.6.0, 8.6.33, 9.6.0-alpha.7 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
parse-server parseplatform	`= 9.6.0≥ 9.0.0, < 9.6.0< 8.6.33`	`9.6.08.6.33`
parse-server npm	`≥ 9.0.0-alpha.1, < 9.6.0-alpha.7< 8.6.33`	`9.6.0-alpha.78.6.33`

Mô tả

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

Mô tả của NVD

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.7 and 8.6.33, 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. This vulnerability is fixed in 9.6.0-alpha.7 and 8.6.33.