CVE-2022-24802 json
Prototype Pollution in deepmerge-ts
published 2022-03-31 4 y ago modified 2026-06-17 4 mo ago also GHSA-r9w3-g83q-m6hq , EUVD-2022-1823
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
deepmerge-ts is a typescript library providing functionality to deep merging of javascript objects. deepmerge-ts is vulnerable to Prototype Pollution via file deepmerge.ts, function defaultMergeRecords(). This issue has been patched in version 4.0.2. There are no known workarounds for this issue.
Patch / fix
- npm deepmerge-ts 4.0.2
- deepmerge-ts_project deepmerge-ts 4.0.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | deepmerge-ts | <4.0.2 |
4.0.2 |
Affected products
- RebeccaStevens deepmerge-ts
Classification
References
-
github.com
/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72
web, patch, third-party-advisory
-
github.com
/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b
web, patch, third-party-advisory
-
github.com
/RebeccaStevens/deepmerge-ts/security/advisories/GHSA-r9w3-g83q-m6hq
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-24802
advisory
-
github.com
/RebeccaStevens/deepmerge-ts
package
Sources
- CVE List CVE-2022-24802
- GitHub Advisory GHSA-r9w3-g83q-m6hq
- NVD CVE-2022-24802
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.