Answer in brief
CVE-2026-109954 records a High severity (CVSS 8.3) vulnerability in Parse Server 9.0.0 before 9.10.2-alpha.5 Transactional Batch Request Write Interference. The current sources do not mark it as known exploited. The current feed maps parse-community/parse-server (generic), parse-community/parse-server (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps parse-community/parse-server (generic), parse-community/parse-server (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| parse-community/parse-servergeneric | >=9.0.0 <9.10.2-alpha.5 | 9.10.2-alpha.5 |
| parse-community/parse-servergeneric | >=5.4.0 <8.6.96 | 8.6.96 |
Published upstream
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 13, 2026
Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client's transactional batch request interfere with other clients' database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients' acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.
Quoted source text, attributed separately from HOL analysis.