This entry duplicated another and was withdrawn in its favour.
Superseded by ETK-2026-1471.
ETK-2026-188Zero's internal tracking ID, independent of the CVE number.
withdrawndescription
Affected Parse Server deployments can share transactional database state across concurrent client requests. A client submitting a transactional batch may cause other clients' writes to be rolled back, rejected, or, on PostgreSQL, blocked by an unclosed transaction when the listed runtime configuration patterns are used.
mitigation
Upgrade the npm parse-server package to 8.6.96 or 9.10.2-alpha.5, as appropriate for the deployed release line. Until upgraded, use a string for masterKey and avoid adding rate-limited Cloud Code validators or changing Parse.Server after startup.
fixed in 9.10.2-alpha.5, 8.6.96
outcome
No artifact: an exploit or check was attempted but could not be produced at this moment.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
No signals recorded for this entry yet.
this entry in the feed
GET /api/v1/feed/ETK-2026-188
{ "etk_id": "ETK-2026-188", "cve_id": null, "display_id": "ETK-2026-188", "ghsa_id": null, "euvd_id": null, "status": "retired", "anchor_state": "awaiting_cve", "title": "Cross-request transaction interference in Parse Server", "summary": "Affected Parse Server deployments can share transactional database state across concurrent client requests. A client submitting a transactional batch may cause other clients' writes to be rolled back, rejected, or, on PostgreSQL, blocked by an unclosed transaction when the listed runtime configuration patterns are used.", "mitigation": "Upgrade the npm parse-server package to 8.6.96 or 9.10.2-alpha.5, as appropriate for the deployed release line. Until upgraded, use a string for masterKey and avoid adding rate-limited Cloud Code validators or changing Parse.Server after startup.", "vendor": "npm", "product": "parse-server", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 9.0.0, < 9.10.2-alpha.5" ], "ecosystem": "npm", "fixed_versions": [ "9.10.2-alpha.5" ], "package_name": "parse-server", "purl": "pkg:npm/parse-server" }, { "affected_notes": [], "affected_ranges": [ ">= 5.4.0, < 8.6.96" ], "ecosystem": "npm", "fixed_versions": [ "8.6.96" ], "package_name": "parse-server", "purl": "pkg:npm/parse-server" } ], "cwes": [ 362 ], "cvss_score": 8.3, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": null, "t0_at": null, "signals": {} }
published 2026-10-01 01:54Z
last change 2026-10-13 15:25Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.