# CVE-2023-26102: rangy vulnerable to Prototype Pollution

> Prototype pollution in the rangy library allows attackers to modify Object.prototype, 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2023
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-65rp-mhqf-8gj3

## What is CVE-2023-26102?

CVE-2023-26102 is a high-severity vulnerability in rangy, published on 24 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the package rangy are vulnerable to Prototype Pollution when using the extend() function in file rangy-core.js.The function uses recursive merge which can lead an attacker to modify properties of the Object.prototype

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

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

2 open source packages ship an affected version, including rangy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rangy` | npm | All versions to 1.3.1 | None |
| `rangy` | npm | All versions to 1.3.1 | None |

Products: Rangy Project Rangy.

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

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

## Is CVE-2023-26102 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26102 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-26102 is a high-severity vulnerability in rangy, published on 24 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26102 exists.

Affected packages and fixed versions:
- rangy (npm): affected all versions up to 1.3.1; no fix listed
- rangy (npm): affected all versions up to 1.3.1; 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-26102/ (Markdown: https://insights.sbomify.com/CVE-2023-26102/index.md)
```

## Sources

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

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