CVE-2026-107353: ljharb traverse · Prototype Pollution
Affects ljharb traverseSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium · fixed in 0.6.12 : update ljharb traverse when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.12, 0.5.3, 0.4.7 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade ljharb traverse to 0.6.12, 0.5.3, 0.4.7 or 0.3.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ljharbtraverse | Affected
| Fixed in
|
| ljharbtraverse | Affected
| Fixed in
|
| ljharbtraverse | Affected
| Fixed in
|
| ljharbtraverse | Affected
| Fixed in
|
npmtraversepkg:npm/traverseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the traverse package to one of the fixed versions: 0.3.10, 0.4.7, 0.5.3, or 0.6.12 or later. No other mitigation is indicated by the vendor advisory. Patch status is confirmed with official fixes available in these versions.
Description
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.