traverse (npm) versions 0.3.6 through 0.3.9, 0.4.0 through 0.4.6, 0.5.0 through 0.5.2, and 0.6.0 through 0.6.11 allow prototype pollution through set(). When the path passed to set() crosses a primitive value, the next path segment is resolved on that primitive's built-in prototype, so an application that passes an untrusted path to set() lets an attacker add or overwrite properties of String.prototype, Number.prototype, or Boolean.prototype using plain JSON data, for example traverse({ name: 'bob' }).set(['name', 'proto', 'polluted'], 'yes'). Object.prototype was reachable only with a non-data path segment, such as an object whose toString returns a different value on each call, or through a Proxy that accepts an assignment without storing it. This is fixed in 0.3.10, 0.4.7, 0.5.3, and 0.6.12.
{
"cna_assigner": "harborist",
"cwe_ids": [
"CWE-1321"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/107xxx/CVE-2026-107353.json"
}{
"extracted_events": [
{
"introduced": "0.3.6"
},
{
"fixed": "0.3.10"
},
{
"introduced": "0.4.0"
},
{
"fixed": "0.4.7"
},
{
"introduced": "0.5.0"
},
{
"fixed": "0.5.3"
},
{
"introduced": "0.6.0"
},
{
"fixed": "0.6.12"
}
],
"source": "AFFECTED_FIELD"
}