Medium · CVSS 6.0CVE-2026-119569

Parse Server 9.0.0 before 9.10.5-alpha.9 Prototype Pollution Denial of ServiceCVE-2026-119569

Answer in brief

CVE-2026-119569 records a Medium severity (CVSS 6.0) vulnerability in Parse Server 9.0.0 before 9.10.5-alpha.9 Prototype Pollution Denial of Service. 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.

Published Oct 30, 2026Updated Oct 30, 2026Source checked Oct 30, 2026First seen by HOL Oct 30, 2026Material review Oct 30, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.0
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 6.0. 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.

Affected scope and exposure questions

The current feed maps parse-community/parse-server (generic), parse-community/parse-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
parse-community/parse-servergeneric	>=9.0.0 <9.10.5-alpha.9	9.10.5-alpha.9
parse-community/parse-servergeneric	>=0 <8.6.108	8.6.108

Recommended response

Check inventory. Check lockfiles and deployed manifests for parse-community/parse-server, parse-community/parse-server.
Review the reported fix. Update parse-community/parse-server to 9.10.5-alpha.9; parse-community/parse-server to 8.6.108 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 30, 2026

Sources and claim methodology

Upstream source description

Parse Server before 8.6.108 and 9.0.0 before 9.10.5-alpha.9 contains a prototype pollution vulnerability because user-controlled keys are expanded into objects without own-property checks. Clients with class write access can send dot notation field keys or ACL entry names matching built-in object members to corrupt built-in functions, causing all requests to fail until server restart.

Quoted source text, attributed separately from HOL analysis.

Affected scope and exposure questions

The current feed maps parse-community/parse-server (generic), parse-community/parse-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
parse-community/parse-servergeneric	>=9.0.0 <9.10.5-alpha.9	9.10.5-alpha.9
parse-community/parse-servergeneric	>=0 <8.6.108	8.6.108

Recommended response

Check inventory. Check lockfiles and deployed manifests for parse-community/parse-server, parse-community/parse-server.

Review the reported fix. Update parse-community/parse-server to 9.10.5-alpha.9; parse-community/parse-server to 8.6.108 if you use the affected versions. Test the change in a non-production environment first.

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.