UBUNTU-CVE-2026-107353 (CVE-2026-107353)
Vulnerability from osv_ubuntu – Published: 2026-10-08 00:00 – Updated: 2026-10-08 00:00 – Source websitetraverse (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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-traverse",
"binary_version": "0.6.1-1"
},
{
"binary_name": "node-traverse",
"binary_version": "0.6.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "node-traverse",
"purl": "pkg:deb/ubuntu/node-traverse@0.6.1-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-traverse",
"binary_version": "0.6.6-1"
},
{
"binary_name": "node-traverse",
"binary_version": "0.6.6-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "node-traverse",
"purl": "pkg:deb/ubuntu/node-traverse@0.6.6-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6.1-1",
"0.6.6-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-traverse",
"binary_version": "0.6.6-2"
},
{
"binary_name": "node-traverse",
"binary_version": "0.6.6-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "node-traverse",
"purl": "pkg:deb/ubuntu/node-traverse@0.6.6-2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6.6-1.1",
"0.6.6-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-traverse",
"binary_version": "0.6.6+~0.6.32-1"
},
{
"binary_name": "node-traverse",
"binary_version": "0.6.6+~0.6.32-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "node-traverse",
"purl": "pkg:deb/ubuntu/node-traverse@0.6.6+~0.6.32-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6.6-2",
"0.6.6+~0.6.32-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-traverse",
"binary_version": "0.6.7+~0.6.32-1"
},
{
"binary_name": "node-traverse",
"binary_version": "0.6.7+~0.6.32-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "node-traverse",
"purl": "pkg:deb/ubuntu/node-traverse@0.6.7+~0.6.32-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6.7+~0.6.32-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-traverse",
"binary_version": "0.6.7+~0.6.32-1"
},
{
"binary_name": "node-traverse",
"binary_version": "0.6.7+~0.6.32-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "node-traverse",
"purl": "pkg:deb/ubuntu/node-traverse@0.6.7+~0.6.32-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6.7+~0.6.32-1"
]
}
],
"aliases": [],
"details": "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\u0027s 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: \u0027bob\u0027 }).set([\u0027name\u0027, \u0027__proto__\u0027, \u0027polluted\u0027], \u0027yes\u0027). 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.",
"id": "UBUNTU-CVE-2026-107353",
"modified": "2026-10-08T00:00:00Z",
"published": "2026-10-08T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-107353"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107353"
},
{
"type": "REPORT",
"url": "https://github.com/ljharb/js-traverse/security/advisories/GHSA-rj28-8w7x-jmqc"
},
{
"type": "REPORT",
"url": "https://github.com/ljharb/js-traverse/commit/81ccab43e379cf42eb2a5f689630f7f79b3d71b8"
},
{
"type": "REPORT",
"url": "https://github.com/ljharb/js-traverse/commit/37a9ebd103d2a259c824c29cdcc3f0dfe1acffce"
},
{
"type": "REPORT",
"url": "https://github.com/ljharb/js-traverse/commit/37a9ebd103d2a259c824c29cdcc3f0dfe1acffce"
},
{
"type": "REPORT",
"url": "https://github.com/ljharb/js-traverse/commit/81ccab43e379cf42eb2a5f689630f7f79b3d71b8"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-107353"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.