Advisory

GHSA-mmpq-5hcv-hf2v

Also known as: BIT-parse-2026-39321, CVE-2026-39321

Summary

Parse Server has a login timing side-channel reveals user existence

Details

Impact

The login endpoint response time differs measurably depending on whether the submitted username or email exists in the database. When a user is not found, the server responds immediately. When a user exists but the password is wrong, a bcrypt comparison runs first, adding significant latency. This timing difference allows an unauthenticated attacker to enumerate valid usernames.

Patches

A dummy bcrypt comparison is now performed when no user is found, normalizing response timing regardless of user existence. Additionally, accounts without a stored password (e.g. OAuth-only) now also run a dummy comparison to prevent the same timing oracle.

Workarounds

Configure rate limiting on the login endpoint to slow automated enumeration. This reduces throughput but does not eliminate the timing signal for individual requests.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-08 00:07 UTC
Modified
2026-04-15 21:34 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.8.0-alpha.6 (semver)

Fixed versions

9.8.0-alpha.6

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.74 (semver)

Fixed versions

8.6.74

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences