CVE-2023-26139 json
underscore-keypath vulnerable to Prototype Pollution
published 3y ago modified 4mo ago also GHSA-gpvc-mx6g-cchv , EUVD-2023-2296
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
Versions of the package underscore-keypath from 0.0.11 are vulnerable to Prototype Pollution via the name argument of the setProperty() function. Exploiting this vulnerability is possible due to improper input sanitization which allows the usage of arguments like “__proto__”.
Is CVE-2023-26139 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | underscore-keypath | >=0.0.11, <=0.9.3 |
no fix listed |
Affected products
- n/a underscore-keypath
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
security.snyk.io
/vuln/SNYK-JS-UNDERSCOREKEYPATH-5416714
web, third-party-advisory
-
gist.github.com
/lelecolacola123/cc0d1e73780127aea9482c05f2ff3252
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-26139
advisory
-
github.com
/jeeeyul/underscore-keypath
package
Sources
- CVE List CVE-2023-26139
- GitHub Advisory GHSA-gpvc-mx6g-cchv
- NVD CVE-2023-26139
Fencer Intel 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.