PULSE
FEED
ransomakira reclama a Krishnanransomakira reclama a Erowa · CH · Manufacturingransomn0n reclama a Company #132 · USransomn0n reclama a Company #131 · DEransomn0n reclama a Company #130 · USransomn0n reclama a Company #129 · USransomn0n reclama a Company #128 · USransomrhysida reclama a Juge, Napolitano, Ruli, Putfark & Pittman · Professional Servicesransompear reclama a gWorks · US · Otherransompear reclama a Palm Vascular Centers · US · Healthcareransomscarlettgroup reclama a sigsauer.com · US · Manufacturingransomdoommageddon reclama a ASLAN TEKSTİL ve KONFEKSİYON San.ve Tic. A.Ş. · TR · Manufacturingransombyod reclama a IHG Hotels & Resorts (Estate) · GB · Hospitalityransomaoqin reclama a SILIKO d.o.o. · SI · Manufacturingransomakira reclama a Krishnanransomakira reclama a Erowa · CH · Manufacturingransomn0n reclama a Company #132 · USransomn0n reclama a Company #131 · DEransomn0n reclama a Company #130 · USransomn0n reclama a Company #129 · USransomn0n reclama a Company #128 · USransomrhysida reclama a Juge, Napolitano, Ruli, Putfark & Pittman · Professional Servicesransompear reclama a gWorks · US · Otherransompear reclama a Palm Vascular Centers · US · Healthcareransomscarlettgroup reclama a sigsauer.com · US · Manufacturingransomdoommageddon reclama a ASLAN TEKSTİL ve KONFEKSİYON San.ve Tic. A.Ş. · TR · Manufacturingransombyod reclama a IHG Hotels & Resorts (Estate) · GB · Hospitalityransomaoqin reclama a SILIKO d.o.o. · SI · Manufacturing
← All CVEs
CVE WatchNov 4, 2026

CVE-2026-121965

Parse Server before 8.6.113 and 9.0.0 before 9.10.6-alpha.5 contains a prototype pollution vulnerability when building objects for Cloud Cod

CVSS

5.3

Medium

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 4, 2026 · Last modified: Nov 4, 2026 · CWE-1321

EPSS · 30d

Not enough EPSS history yet.

Technical description

Parse Server before 8.6.113 and 9.0.0 before 9.10.6-alpha.5 contains a prototype pollution vulnerability when building objects for Cloud Code triggers and LiveQuery, where a dot notation key whose intermediate segment resolves through an inherited member writes onto a process-wide built-in. Clients with write access to an object in a class with a trigger or LiveQuery can corrupt a built-in function, making unrelated requests fail until restart and denying service to all clients and hosted applications.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-634025.9 MED
18.3%
——6i18next is an internationalization framework for JavaScript. Prior to version 26.3.4, `deepExtend` in `src/utils.js` checks property existence with the in operator and recurses into inherited built-ins reached through `Object.prototype`. An application must explicitly pass attacker-controlled resource data to `addResourceBundle(lng, ns, data, deep, overwrite)` with both `deep: true` and `overwrite: true`. Source keys such as `hasOwnProperty`, `toString` and `valueOf` can then select shared inherited built-in function objects, and a nested value can overwrite a property of those objects process-wide. For example, making `Object.prototype.hasOwnProperty.call` non-callable causes subsequent uses, including i18next internals, to throw TypeError, resulting in unrecoverable denial of service and limited integrity impact. The `__proto__`/`constructor` guard does not prevent this mechanism because the corruption target is an inherited built-in function rather than the prototype object itself. Default calls without deep merging or with overwrite falsy are unaffected, and no standard i18next backend or integration uses the vulnerable configuration. This issue is distinct from the setPath/key-walking prototype-pollution flaws in i18next-fs-backend (CVE-2026-48713) and i18next-http-middleware (CVE-2026-48714). This issue is fixed in version 26.3.4.2d
CVE-2026-1195695.3 MED
31.8%
——10Parse 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.5d
CVE-2026-1187774.8 MED
17.2%
——5Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the forge.http client stored cookie names and paths from Set-Cookie response headers in ordinary JavaScript objects. A malicious server could use the cookie name __proto__ so that the attacker-controlled cookie path was written as a property on Object.prototype, or use inherited names such as constructor to modify Object. An empty cookie value could use the removal path to delete an inherited Object.prototype property. Applications using forge.http directly or through forge.xhr are affected; applications that do not use forge.http are unaffected. This issue is fixed in version 1.4.1.3h
CVE-2026-1186787.1 HIG
22.0%
——7n8n before 2.41.4 and 2.42.x before 2.42.1 contains a prototype pollution vulnerability that allows low-privileged users to alter built-in object behaviour by saving workflows with specially named connection keys. Attackers can add keys such as __proto__ to workflow connections, which the periodic history compaction task processes, causing logins and writes to fail with server errors.6d
CVE-2026-1186498.3 HIG
19.3%
——6n8n before 2.43.5 and 2.44.x before 2.44.1 accepts a client-supplied workflow ID and caches each workflow's owner project in memory by that ID, so a crafted ID such as __proto__ makes the Data Table project check match every project. An authenticated member who can create and run workflows can list, read, modify, and delete Data Table rows in all projects of the instance.6d
CVE-2026-118250—
30.2%
——9Highcharts JS is a JavaScript charting library based on SVG. From 6.1.0 until 11.4.9, 12.6.1, and 3.1.0, Highcharts follows dot-separated series.keys paths without filtering each segment. An attacker who controls series.keys and matching point data can use a path through __proto__ to assign arbitrary named properties to Object.prototype. Those properties are visible to all JavaScript in the page, and no user interaction is required beyond rendering the chart. This issue is fixed in 11.4.9, 12.6.1, and 3.1.0.1d