DEBIAN-CVE-2026-107353
- Source
- https://security-tracker.debian.org/tracker/CVE-2026-107353
- Import Source
- https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-107353.json
- JSON Data
- https://api.osv.dev/v1/vulns/DEBIAN-CVE-2026-107353
- Upstream
- Published
- 2026-10-07T20:17:11Z
- Modified
- 2026-10-09T09:47:27Z
- Severity
-
- 6.9 (Medium) CVSS_V4 - 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X CVSS Calculator
- Summary
- [none]
- 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'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.
- References
Affected packages
Debian:12 / node-traverse
Package
- Name
- node-traverse
- Purl
- pkg:deb/debian/node-traverse?arch=source&distro=bookworm
Debian:13 / node-traverse
Package
- Name
- node-traverse
- Purl
- pkg:deb/debian/node-traverse?arch=source&distro=trixie
Debian:14 / node-traverse
Package
- Name
- node-traverse
- Purl
- pkg:deb/debian/node-traverse?arch=source&distro=forky