# CVE-2023-26139: underscore-keypath vulnerable to Prototype Pollution

> Prototype pollution in underscore-keypath allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-gpvc-mx6g-cchv

## What is CVE-2023-26139?

CVE-2023-26139 is a high-severity vulnerability in underscore-keypath, published on 1 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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__”.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2023-26139?

2 open source packages ship an affected version, including underscore-keypath. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `underscore-keypath` | npm | From 0.0.11 to 0.9.3 | None |
| `underscore-keypath` | npm | From 0.0.11 to 0.9.3 | None |

Products: Underscore-Keypath Project Underscore-Keypath.

## How do I fix CVE-2023-26139?

No fix has been published for CVE-2023-26139 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-26139 being exploited?

There is no known exploitation of CVE-2023-26139 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26139 and fix it if it is affected.

What it is: CVE-2023-26139 is a high-severity vulnerability in underscore-keypath, published on 1 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-26139 in the wild and no public exploit code.

Affected packages and fixed versions:
- underscore-keypath (npm): affected from 0.0.11 up to 0.9.3; no fix listed
- underscore-keypath (npm): affected from 0.0.11 up to 0.9.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-26139/ (Markdown: https://insights.sbomify.com/CVE-2023-26139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26139
- OSV: https://osv.dev/vulnerability/CVE-2023-26139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-26139/
Summaries are generated and may contain mistakes; the official description above is the record.