CWE-1321
AllowedImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Abstraction: Variant · Status: Incomplete
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
859 vulnerabilities reference this CWE, most recent first.
GHSA-95FF-46G6-6GW9
Vulnerability from github – Published: 2026-01-28 21:41 – Updated: 2026-01-28 21:41Summary
An authenticated user with org-level-creator permissions can exploit prototype pollution in the /api/v2/meta/connection/test endpoint, causing all database write operations to fail application-wide until server restart.
While the pollution technically bypasses SUPER_ADMIN authorization checks, no practical privileged actions can be performed because database operations fail immediately after pollution.
Details
The deepMerge() function in packages/nocodb/src/utils/dataUtils.ts does not sanitize the following keys: (__proto__, constructor, prototype):
export const deepMerge = (target: any, ...sources: any[]) => {
// ...
Object.keys(source).forEach((key) => {
if (isMergeableObject(source[key])) {
if (!target[key]) target[key] = Array.isArray(source[key]) ? [] : {};
deepMerge(target[key], source[key]); // Recursively merges __proto__
} else {
target[key] = source[key];
}
});
// ...
};
The testConnection endpoint (packages/nocodb/src/controllers/utils.controller.ts) passes user-controlled input directly to deepMerge():
config = await integration.getConfig();
deepMerge(config, body);
When an attacker sends {"__proto__": {"super": true}}, the super property is written to Object.prototype, affecting all plain objects in the Node.js process.
Impact
Pollutes Object.prototype globally, breaking all subsequent database write operations for all users until process restart.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "nocodb"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.301.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-24766"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2026-01-28T21:41:26Z",
"nvd_published_at": "2026-01-28T21:16:12Z",
"severity": "MODERATE"
},
"details": "### Summary\n\nAn authenticated user with org-level-creator permissions can exploit prototype pollution in the `/api/v2/meta/connection/test` endpoint, causing all database write operations to fail application-wide until server restart.\n\nWhile the pollution technically bypasses SUPER_ADMIN authorization checks, no practical privileged actions can be performed because database operations fail immediately after pollution.\n\n### Details\n\nThe `deepMerge()` function in `packages/nocodb/src/utils/dataUtils.ts` does not sanitize the following keys: (`__proto__`, `constructor`, `prototype`):\n\n```typescript\nexport const deepMerge = (target: any, ...sources: any[]) =\u003e {\n // ...\n Object.keys(source).forEach((key) =\u003e {\n if (isMergeableObject(source[key])) {\n if (!target[key]) target[key] = Array.isArray(source[key]) ? [] : {};\n deepMerge(target[key], source[key]); // Recursively merges __proto__\n } else {\n target[key] = source[key];\n }\n });\n // ...\n};\n```\n\nThe `testConnection` endpoint (`packages/nocodb/src/controllers/utils.controller.ts`) passes user-controlled input directly to `deepMerge()`:\n\n```typescript\nconfig = await integration.getConfig();\ndeepMerge(config, body);\n```\n\nWhen an attacker sends `{\"__proto__\": {\"super\": true}}`, the `super` property is written to `Object.prototype`, affecting all plain objects in the Node.js process.\n\n## Impact\n\nPollutes Object.prototype globally, breaking all subsequent database write operations for all users until process restart.",
"id": "GHSA-95ff-46g6-6gw9",
"modified": "2026-01-28T21:41:26Z",
"published": "2026-01-28T21:41:26Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-95ff-46g6-6gw9"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24766"
},
{
"type": "PACKAGE",
"url": "https://github.com/nocodb/nocodb"
},
{
"type": "WEB",
"url": "https://github.com/nocodb/nocodb/releases/tag/0.301.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "NocoDB has Prototype Pollution in Connection Test Endpoint, Leading to DoS"
}
GHSA-95JQ-XPH2-CX9H
Vulnerability from github – Published: 2025-07-26 00:30 – Updated: 2026-06-26 20:26Prototype Pollution in internal assign() helper in Linkify allows remote attackers to execute arbitrary JavaScript (Stored or Reflected XSS) via injection of event handlers through unfiltered proto property. This issue affects Linkify version 4.3.1 and is fixed in 4.3.2.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "linkifyjs"
},
"ranges": [
{
"events": [
{
"introduced": "4.3.1"
},
{
"fixed": "4.3.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.3.1"
]
}
],
"aliases": [
"CVE-2025-8101"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2025-07-29T19:09:33Z",
"nvd_published_at": "2025-07-25T22:15:25Z",
"severity": "HIGH"
},
"details": "Prototype Pollution in internal `assign()` helper in Linkify allows remote attackers to execute arbitrary JavaScript (Stored or Reflected XSS) via injection of event handlers through unfiltered proto property. This issue affects Linkify version 4.3.1 and is fixed in 4.3.2.",
"id": "GHSA-95jq-xph2-cx9h",
"modified": "2026-06-26T20:26:11Z",
"published": "2025-07-26T00:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8101"
},
{
"type": "WEB",
"url": "https://github.com/nfrasser/linkifyjs/commit/931d3e28b68951b8f898ea4d6504696346b485b0"
},
{
"type": "WEB",
"url": "https://caverav.cl/posts/linkify-xss/linkify-xss"
},
{
"type": "WEB",
"url": "https://fluidattacks.com/advisories/charly"
},
{
"type": "PACKAGE",
"url": "https://github.com/nfrasser/linkifyjs"
},
{
"type": "WEB",
"url": "https://github.com/nfrasser/linkifyjs/releases/tag/v4.3.2"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/package/linkifyjs"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Linkify Allows Prototype Pollution \u0026 HTML Attribute Injection (XSS)"
}
GHSA-97JV-C342-5XHC
Vulnerability from github – Published: 2022-12-19 15:30 – Updated: 2022-12-29 23:37A vulnerability classified as critical has been found in Furqan node-whois. Affected is an unknown function of the file index.coffee. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). It is possible to launch the attack remotely. The name of the patch is 46ccc2aee8d063c7b6b4dee2c2834113b7286076. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-216252.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "whois"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-36618"
],
"database_specific": {
"cwe_ids": [
"CWE-1321",
"CWE-74",
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2022-12-19T18:24:03Z",
"nvd_published_at": "2022-12-19T14:15:00Z",
"severity": "CRITICAL"
},
"details": "A vulnerability classified as critical has been found in Furqan node-whois. Affected is an unknown function of the file `index.coffee`. The manipulation leads to improperly controlled modification of object prototype attributes (\u0027prototype pollution\u0027). It is possible to launch the attack remotely. The name of the patch is 46ccc2aee8d063c7b6b4dee2c2834113b7286076. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-216252.",
"id": "GHSA-97jv-c342-5xhc",
"modified": "2022-12-29T23:37:10Z",
"published": "2022-12-19T15:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-36618"
},
{
"type": "WEB",
"url": "https://github.com/FurqanSoftware/node-whois/pull/105"
},
{
"type": "WEB",
"url": "https://github.com/FurqanSoftware/node-whois/commit/46ccc2aee8d063c7b6b4dee2c2834113b7286076"
},
{
"type": "PACKAGE",
"url": "https://github.com/FurqanSoftware/node-whois"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.216252"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20220403104013/https://www.npmjs.com/package/whois"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "FurqanSoftware/node-whois vulnerable to Prototype Pollution"
}
GHSA-97VM-C39P-JR86
Vulnerability from github – Published: 2025-08-13 21:30 – Updated: 2026-06-09 11:56Spreecommerce versions prior to 0.60.2 contains a remote command execution vulnerability in its search functionality. The application fails to properly sanitize input passed via the search[send][] parameter, which is dynamically invoked using Ruby’s send method. This allows attackers to execute arbitrary shell commands on the server without authentication.
{
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "spree"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.60.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2011-10019"
],
"database_specific": {
"cwe_ids": [
"CWE-1321",
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2026-01-13T20:33:40Z",
"nvd_published_at": "2025-08-13T21:15:29Z",
"severity": "CRITICAL"
},
"details": "Spreecommerce versions prior to 0.60.2 contains a remote command execution vulnerability in its search functionality. The application fails to properly sanitize input passed via the search[send][] parameter, which is dynamically invoked using Ruby\u2019s send method. This allows attackers to execute arbitrary shell commands on the server without authentication.",
"id": "GHSA-97vm-c39p-jr86",
"modified": "2026-06-09T11:56:05Z",
"published": "2025-08-13T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-10019"
},
{
"type": "WEB",
"url": "https://github.com/orgs/spree"
},
{
"type": "WEB",
"url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree/CVE-2011-10019.yml"
},
{
"type": "PACKAGE",
"url": "https://github.com/spree/spree"
},
{
"type": "WEB",
"url": "https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/http/spree_search_exec.rb"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20111009192436/http://spreecommerce.com/blog/2011/10/05/remote-command-product-group"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/17941"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/spreecommerce-search-parameter-rce"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
"type": "CVSS_V4"
}
],
"summary": "Spree has Remote Command Execution vulnerability in search functionality"
}
GHSA-9829-JJ5P-J6HF
Vulnerability from github – Published: 2021-05-06 18:26 – Updated: 2021-05-05 17:39All versions up to and including 1.0.0 of the package worksmith are vulnerable to Prototype Pollution via the setValue function.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "worksmith"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-7725"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2021-05-05T17:39:52Z",
"nvd_published_at": "2020-09-01T10:15:00Z",
"severity": "CRITICAL"
},
"details": "All versions up to and including 1.0.0 of the package worksmith are vulnerable to Prototype Pollution via the setValue function.",
"id": "GHSA-9829-jj5p-j6hf",
"modified": "2021-05-05T17:39:52Z",
"published": "2021-05-06T18:26:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-7725"
},
{
"type": "WEB",
"url": "https://snyk.io/vuln/SNYK-JS-WORKSMITH-598798"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Prototype Pollution in worksmith"
}
GHSA-992F-WF4W-X36V
Vulnerability from github – Published: 2020-09-01 21:16 – Updated: 2020-08-31 18:33All versions of merge-objects are vulnerable to Prototype Pollution.
Recommendation
No fix is available for this vulnerability at this time. It is our recommendation to use an alternative package.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "merge-objects"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2020-08-31T18:33:09Z",
"nvd_published_at": null,
"severity": "LOW"
},
"details": "All versions of `merge-objects` are vulnerable to Prototype Pollution.\n\n\n## Recommendation\n\nNo fix is available for this vulnerability at this time. It is our recommendation to use an alternative package.",
"id": "GHSA-992f-wf4w-x36v",
"modified": "2020-08-31T18:33:09Z",
"published": "2020-09-01T21:16:13Z",
"references": [
{
"type": "WEB",
"url": "https://hackerone.com/reports/310706"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/716"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Prototype Pollution in merge-objects"
}
GHSA-9C47-M6QQ-7P4H
Vulnerability from github – Published: 2022-12-29 01:51 – Updated: 2024-02-13 21:31The parse method of the JSON5 library before and including version 2.2.1 does not restrict parsing of keys named __proto__, allowing specially crafted strings to pollute the prototype of the resulting object.
This vulnerability pollutes the prototype of the object returned by JSON5.parse and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations.
Impact
This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from JSON5.parse. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution.
Mitigation
This vulnerability is patched in json5 v2.2.2 and later. A patch has also been backported for json5 v1 in versions v1.0.2 and later.
Details
Suppose a developer wants to allow users and admins to perform some risky operation, but they want to restrict what non-admins can do. To accomplish this, they accept a JSON blob from the user, parse it using JSON5.parse, confirm that the provided data does not set some sensitive keys, and then performs the risky operation using the validated data:
const JSON5 = require('json5');
const doSomethingDangerous = (props) => {
if (props.isAdmin) {
console.log('Doing dangerous thing as admin.');
} else {
console.log('Doing dangerous thing as user.');
}
};
const secCheckKeysSet = (obj, searchKeys) => {
let searchKeyFound = false;
Object.keys(obj).forEach((key) => {
if (searchKeys.indexOf(key) > -1) {
searchKeyFound = true;
}
});
return searchKeyFound;
};
const props = JSON5.parse('{"foo": "bar"}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
doSomethingDangerous(props); // "Doing dangerous thing as user."
} else {
throw new Error('Forbidden...');
}
If the user attempts to set the isAdmin key, their request will be rejected:
const props = JSON5.parse('{"foo": "bar", "isAdmin": true}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
doSomethingDangerous(props);
} else {
throw new Error('Forbidden...'); // Error: Forbidden...
}
However, users can instead set the __proto__ key to {"isAdmin": true}. JSON5 will parse this key and will set the isAdmin key on the prototype of the returned object, allowing the user to bypass the security check and run their request as an admin:
js
const props = JSON5.parse('{"foo": "bar", "__proto__": {"isAdmin": true}}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
doSomethingDangerous(props); // "Doing dangerous thing as admin."
} else {
throw new Error('Forbidden...');
}
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "json5"
},
"ranges": [
{
"events": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.2.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "json5"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-46175"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2022-12-29T01:51:03Z",
"nvd_published_at": "2022-12-24T04:15:00Z",
"severity": "HIGH"
},
"details": "The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object.\n\nThis vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations.\n\n## Impact\nThis vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution.\n\n## Mitigation\nThis vulnerability is patched in json5 v2.2.2 and later. A patch has also been backported for json5 v1 in versions v1.0.2 and later.\n\n## Details\n \nSuppose a developer wants to allow users and admins to perform some risky operation, but they want to restrict what non-admins can do. To accomplish this, they accept a JSON blob from the user, parse it using `JSON5.parse`, confirm that the provided data does not set some sensitive keys, and then performs the risky operation using the validated data:\n \n```js\nconst JSON5 = require(\u0027json5\u0027);\n\nconst doSomethingDangerous = (props) =\u003e {\n if (props.isAdmin) {\n console.log(\u0027Doing dangerous thing as admin.\u0027);\n } else {\n console.log(\u0027Doing dangerous thing as user.\u0027);\n }\n};\n\nconst secCheckKeysSet = (obj, searchKeys) =\u003e {\n let searchKeyFound = false;\n Object.keys(obj).forEach((key) =\u003e {\n if (searchKeys.indexOf(key) \u003e -1) {\n searchKeyFound = true;\n }\n });\n return searchKeyFound;\n};\n\nconst props = JSON5.parse(\u0027{\"foo\": \"bar\"}\u0027);\nif (!secCheckKeysSet(props, [\u0027isAdmin\u0027, \u0027isMod\u0027])) {\n doSomethingDangerous(props); // \"Doing dangerous thing as user.\"\n} else {\n throw new Error(\u0027Forbidden...\u0027);\n}\n```\n \nIf the user attempts to set the `isAdmin` key, their request will be rejected:\n \n```js\nconst props = JSON5.parse(\u0027{\"foo\": \"bar\", \"isAdmin\": true}\u0027);\nif (!secCheckKeysSet(props, [\u0027isAdmin\u0027, \u0027isMod\u0027])) {\n doSomethingDangerous(props);\n} else {\n throw new Error(\u0027Forbidden...\u0027); // Error: Forbidden...\n}\n```\n \nHowever, users can instead set the `__proto__` key to `{\"isAdmin\": true}`. `JSON5` will parse this key and will set the `isAdmin` key on the prototype of the returned object, allowing the user to bypass the security check and run their request as an admin:\n \n```js\nconst props = JSON5.parse(\u0027{\"foo\": \"bar\", \"__proto__\": {\"isAdmin\": true}}\u0027);\nif (!secCheckKeysSet(props, [\u0027isAdmin\u0027, \u0027isMod\u0027])) {\n doSomethingDangerous(props); // \"Doing dangerous thing as admin.\"\n} else {\n throw new Error(\u0027Forbidden...\u0027);\n}\n ```",
"id": "GHSA-9c47-m6qq-7p4h",
"modified": "2024-02-13T21:31:39Z",
"published": "2022-12-29T01:51:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/json5/json5/security/advisories/GHSA-9c47-m6qq-7p4h"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-46175"
},
{
"type": "WEB",
"url": "https://github.com/json5/json5/issues/199"
},
{
"type": "WEB",
"url": "https://github.com/json5/json5/issues/295"
},
{
"type": "WEB",
"url": "https://github.com/json5/json5/pull/298"
},
{
"type": "WEB",
"url": "https://github.com/json5/json5/commit/62a65408408d40aeea14c7869ed327acead12972"
},
{
"type": "WEB",
"url": "https://github.com/json5/json5/commit/7774c1097993bc3ce9f0ac4b722a32bf7d6871c8"
},
{
"type": "PACKAGE",
"url": "https://github.com/json5/json5"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2023/11/msg00021.html"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3S26TLPLVFAJTUN3VIXFDEBEXDYO22CE"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H",
"type": "CVSS_V3"
}
],
"summary": "Prototype Pollution in JSON5 via Parse Method"
}
GHSA-9CCR-FPP6-78QF
Vulnerability from github – Published: 2026-03-17 18:37 – Updated: 2026-03-19 21:13Impact
An attacker can bypass the default request keyword denylist protection and the class-level permission for adding fields by sending a crafted request that exploits prototype pollution in the deep copy mechanism. This allows injecting fields into class schemas that have field addition locked down, and can cause permanent schema type conflicts that cannot be resolved even with the master key.
Patches
The vulnerable third-party deep copy library has been replaced with a built-in deep clone mechanism that handles prototype properties safely, allowing the existing denylist check to correctly detect and reject the prohibited keyword.
Workarounds
None.
Vulnerability Independence
This vulnerability is not caused by or dependent on a vulnerability in a third-party dependency.
The third-party deepcopy library that was replaced in the fix has no known CVE or security advisory regarding this. The library functions as designed. It is not vulnerable.
The vulnerability is in parse-server's own request processing logic. Parse-server's security-critical keyword denylist check runs after the deep copy step in the request pipeline. The deep copy step strips __proto__ properties as a normal part of its cloning behavior, which means the denylist check never sees the prohibited key. This allows an attacker to bypass both the denylist protection and class-level permissions for adding fields, resulting in schema poisoning.
The root cause is parse-server's reliance on a cloning mechanism that alters the shape of the data before the security check can inspect it. This is a logic flaw in parse-server's security pipeline, not a vulnerability in a dependency. Replacing the cloning mechanism was the fix for parse-server's own bug.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "parse-server"
},
"ranges": [
{
"events": [
{
"introduced": "9.0.0"
},
{
"fixed": "9.6.0-alpha.20"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "parse-server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.6.44"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-32878"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-17T18:37:08Z",
"nvd_published_at": "2026-03-18T22:16:25Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nAn attacker can bypass the default request keyword denylist protection and the class-level permission for adding fields by sending a crafted request that exploits prototype pollution in the deep copy mechanism. This allows injecting fields into class schemas that have field addition locked down, and can cause permanent schema type conflicts that cannot be resolved even with the master key.\n\n### Patches\n\nThe vulnerable third-party deep copy library has been replaced with a built-in deep clone mechanism that handles prototype properties safely, allowing the existing denylist check to correctly detect and reject the prohibited keyword.\n\n### Workarounds\n\nNone.\n\n### Vulnerability Independence\n\nThis vulnerability is not caused by or dependent on a vulnerability in a third-party dependency.\n\nThe third-party `deepcopy` library that was replaced in the fix has no known CVE or security advisory regarding this. The library functions as designed. It is not vulnerable.\n\nThe vulnerability is in parse-server\u0027s own request processing logic. Parse-server\u0027s security-critical keyword denylist check runs after the deep copy step in the request pipeline. The deep copy step strips `__proto__` properties as a normal part of its cloning behavior, which means the denylist check never sees the prohibited key. This allows an attacker to bypass both the denylist protection and class-level permissions for adding fields, resulting in schema poisoning.\n\nThe root cause is parse-server\u0027s reliance on a cloning mechanism that alters the shape of the data before the security check can inspect it. This is a logic flaw in parse-server\u0027s security pipeline, not a vulnerability in a dependency. Replacing the cloning mechanism was the fix for parse-server\u0027s own bug.",
"id": "GHSA-9ccr-fpp6-78qf",
"modified": "2026-03-19T21:13:38Z",
"published": "2026-03-17T18:37:08Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-9ccr-fpp6-78qf"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32878"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/parse-server/pull/10200"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/parse-server/pull/10201"
},
{
"type": "PACKAGE",
"url": "https://github.com/parse-community/parse-server"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Parse Server vulnerable to schema poisoning via prototype pollution in deep copy"
}
GHSA-9F2H-7V79-MXW3
Vulnerability from github – Published: 2025-10-14 22:24 – Updated: 2025-10-14 22:24Summary
Prototype pollution capabilities on various APIs.
Details
Injection of malicious payload allows attacker to remotely execute arbitrary code. Parse.Object and internal APIs are affected, specifically:
- ParseObject.fromJSON
- ParseObject.pin
- ParseObject.registerSubclass
- ObjectStateMutations (internal)
- encode/decode (internal)
PoC
Demonstrative tests added as part of the fix.
References
- https://github.com/parse-community/Parse-SDK-JS/security/advisories/GHSA-9f2h-7v79-mxw3
- Patch https://github.com/parse-community/Parse-SDK-JS/releases/tag/7.0.0-alpha.1
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "parse"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "7.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-62374"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2025-10-14T22:24:10Z",
"nvd_published_at": "2025-10-14T20:15:53Z",
"severity": "MODERATE"
},
"details": "### Summary\n\nPrototype pollution capabilities on various APIs.\n\n### Details\n\nInjection of malicious payload allows attacker to remotely execute arbitrary code. `Parse.Object` and internal APIs are affected, specifically:\n- `ParseObject.fromJSON`\n- `ParseObject.pin`\n- `ParseObject.registerSubclass`\n- `ObjectStateMutations` (internal)\n- `encode`/`decode` (internal)\n\n### PoC\n\nDemonstrative tests added as part of the fix.\n\n### References\n\n- https://github.com/parse-community/Parse-SDK-JS/security/advisories/GHSA-9f2h-7v79-mxw3\n- Patch https://github.com/parse-community/Parse-SDK-JS/releases/tag/7.0.0-alpha.1",
"id": "GHSA-9f2h-7v79-mxw3",
"modified": "2025-10-14T22:24:10Z",
"published": "2025-10-14T22:24:10Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/parse-community/Parse-SDK-JS/security/advisories/GHSA-9f2h-7v79-mxw3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62374"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/Parse-SDK-JS/pull/2749"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/Parse-SDK-JS/commit/00973987f361368659c0c4dbf669f3897520b132"
},
{
"type": "PACKAGE",
"url": "https://github.com/parse-community/Parse-SDK-JS"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/Parse-SDK-JS/releases/tag/7.0.0-alpha.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "Parse Javascript SDK vulnerable to prototype pollution in `Parse.Object` and internal APIs"
}
GHSA-9FP7-4FJM-Q3MF
Vulnerability from github – Published: 2022-02-01 00:51 – Updated: 2022-01-31 19:46The package keyget from 0.0.0 are vulnerable to Prototype Pollution via the methods set, push, and at which could allow an attacker to cause a denial of service and may lead to remote code execution. Note: This vulnerability derives from an incomplete fix to CVE-2020-28272
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "keyget"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.4.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-23760"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2022-01-31T19:46:10Z",
"nvd_published_at": "2022-01-28T22:15:00Z",
"severity": "MODERATE"
},
"details": "The package keyget from 0.0.0 are vulnerable to Prototype Pollution via the methods set, push, and at which could allow an attacker to cause a denial of service and may lead to remote code execution. **Note:** This vulnerability derives from an incomplete fix to [CVE-2020-28272](https://security.snyk.io/vuln/SNYK-JS-KEYGET-1048048)",
"id": "GHSA-9fp7-4fjm-q3mf",
"modified": "2022-01-31T19:46:10Z",
"published": "2022-02-01T00:51:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-23760"
},
{
"type": "PACKAGE",
"url": "https://github.com/rumkin/keyget"
},
{
"type": "WEB",
"url": "https://security.snyk.io/vuln/SNYK-JS-KEYGET-1048048"
},
{
"type": "WEB",
"url": "https://snyk.io/vuln/SNYK-JS-KEYGET-2342624"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "Prototype Pollution in keyget"
}
Mitigation
By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
Mitigation
By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
Mitigation
Strategy: Input Validation
When handling untrusted objects, validating using a schema can be used.
Mitigation
By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.
Mitigation
Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.
CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
CAPEC-180: Exploiting Incorrectly Configured Access Control Security Levels
An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
CAPEC-77: Manipulating User-Controlled Variables
This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.