CVE-2026-55091: flat-to-nested Prototype Pollution Vulnerability
HIGHCVE-2026-55091 is a HIGH (CVSS 7.5) prototype pollution vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting flat-to-nested libraries in the npm ecosystem. The issue involves prototype pollution in flat-to-nested convert() via __proto__ parent/id key. Remediation is available by upgrading affected packages to version 1.1.2.
CVE-2026-55091 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-55091
To remediate this vulnerability, upgrade all affected flat-to-nested dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install flat-to-nested@1.1.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls flat-to-nested
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-55091, inspect your project dependencies using npm:
npm ls flat-to-nested
Analyze the terminal output to locate any version of flat-to-nested in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.2), your application is affected.
Note: The npm ls flat-to-nested command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), where 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. In flat-to-nested, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55091 Affected flat-to-nested Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
flat-to-nested
|
npm |
< 1.1.2
|
1.1.2
|
References
Frequently Asked Questions
What is CVE-2026-55091?
Which flat-to-nested versions are affected?
What version fixes CVE-2026-55091?
Is flat-to-nested affected?
What is the CVSS score of CVE-2026-55091?
What CWE is associated with CVE-2026-55091?
How can I check npm dependencies for CVE-2026-55091?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hp36-v28f-w3r4",
"modified" : "2026-06-19T20:47:52Z",
"published" : "2026-06-19T20:47:52Z",
"aliases" : [ "CVE-2026-55091" ],
"summary" : "flat-to-nested: Prototype pollution in flat-to-nested convert() via __proto__ parent/id key",
"details" : "### Summary\n `convert()` builds the nested tree by using each flat record's `id` and `parent` field values directly as object keys, with no guard against `__proto__` / `constructor` / `prototype`. A record whose `parent` is the string `\"__proto__\"` makes `temp[parent]` resolve to `Object.prototype`, and the following `initPush(...)` writes attacker-controlled data onto the global prototype. Any application that passes attacker-influenced records to `convert()` is affected, and the base prototype methods stay intact so the pollution is stealthy.\n\n ### Details\n In `index.js`, `convert()` (`FlatToNested.prototype.convert`):\n\n - `temp = {}` (line 45) and `pendingChildOf = {}` (line 46) are plain objects, so they inherit from `Object.prototype`.\n - For each record, `parent = flatEl[this.config.parent]` (line 51) is taken verbatim from input.\n - Line 57: `if (temp[parent] !== undefined)` — when `parent === \"__proto__\"`, `temp[\"__proto__\"]` resolves via the prototype chain to `Object.prototype`, which is `!== undefined`, so the\n branch is taken.\n - Line 59: `initPush(this.config.children, temp[parent], flatEl)` → effectively `initPush(\"children\", Object.prototype, flatEl)`.\n - `initPush` (lines 4-9): `Object.prototype[\"children\"] = []` then `Object.prototype[\"children\"].push(flatEl)` — **attacker-controlled data is written onto the global `Object.prototype`.**\n\n There is no sanitization of `id` / `parent` anywhere; they flow straight into `temp[id]`, `temp[parent]`, and `pendingChildOf[parent]` as dynamic keys.\n\n ### PoC\n ```js\n const FlatToNested = require('flat-to-nested');\n\n new FlatToNested().convert([\n { id: 1, parent: '__proto__', polluted: 'PWNED' }\n ]);\n\n console.log(({}).children); // => [ { id: 1, polluted: 'PWNED' } ]\n A freshly-created, unrelated object {} now carries an attacker-controlled children property. ({}).toString === Object.prototype.toString remains true, so existing methods are untouched (stealthy). If the consumer configures a custom children key, that arbitrary prototype property is polluted instead.\n ```\n \n ### Impact\n\n Prototype pollution (CWE-1321). Any service that builds a tree from attacker-influenced flat records (the package's core purpose — e.g. records derived from a DB/REST/user input) can have Object.prototype polluted. Consequences range from application-logic corruption and denial of service to serving as a gadget toward privilege escalation or RCE depending on downstream sinks. No special privileges or user interaction required; the malicious value is ordinary input data.\n\n ### Suggested fix\n\n Use prototype-less lookup tables so inherited keys like __proto__ cannot be reached:\n var temp = Object.create(null);\n var pendingChildOf = Object.create(null);\n (Optionally also reject id/parent values equal to __proto__, constructor, or prototype.) Verified: with Object.create(null) for both temp and pendingChildOf, the PoC no longer pollutes Object.prototype and normal nesting output is unchanged. A patch with a regression test is ready.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "flat-to-nested"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.1.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.1.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/joaonuno/flat-to-nested-js/security/advisories/GHSA-hp36-v28f-w3r4"
}, {
"type" : "WEB",
"url" : "https://github.com/joaonuno/flat-to-nested-js/commit/680a5ebe1194edda16fa93baaa56ff14fe0e3d7f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/joaonuno/flat-to-nested-js"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1321", "CWE-915" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-19T20:47:52Z",
"nvd_published_at" : null
}
}