CVE-2023-26102

HIGHNVD 7.58.2▲Elevated

7.5

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

CVSS v3: 7.5
EG Score: 8.2(medium)
EPSS: 57.9%
KEV: Not listed

Published

February 24, 2023

Last Modified

March 11, 2025

References (4)

report@snykhttps://github.com/timdown/rangy/issues/478
report@snykhttps://security.snyk.io/vuln/SNYK-JS-RANGY-3175702
af854a3a-2127-422b-91ae-364da2661108https://github.com/timdown/rangy/issues/478
af854a3a-2127-422b-91ae-364da2661108https://security.snyk.io/vuln/SNYK-JS-RANGY-3175702

Patch Availability(1)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
npm	rangy	—	ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)

npm(1)

Package	Vulnerable range	Fixed in	Dependents
rangy	—	—	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2023-26102?

CVE-2023-26102 is a high vulnerability published on February 24, 2023. 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

When was CVE-2023-26102 disclosed?

CVE-2023-26102 was first published in the National Vulnerability Database on February 24, 2023, with the most recent update on March 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2023-26102 actively exploited?

CVE-2023-26102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2023-26102?

CVE-2023-26102 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2.

How do I remediate CVE-2023-26102?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-26102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-26102

Explore →

Is Your Infrastructure Affected by CVE-2023-26102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2023-26102

📅 Published

🔄 Last Modified

🔗 References (4)