CVE-2026-48170

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

scim-patch, a library to perform SCIM patch, prior to version 0.9.1 performs prototype pollution when applying a SCIM PATCH operation whose value object contains a key like "__proto__.someProp". After one such patch, Object.prototype.someProp is set process-wide, affecting every plain object in the Node process. Any service that calls scimPatch() on attacker-controlled JSON (i.e. any SCIM endpoint accepting PATCH from an external IdP) is exploitable on a stock Node runtime. Version 0.9.1 contains a patch. A workaround is available. Calling Object.freeze(Object.prototype) (and the same on Array.prototype, Function.prototype) at process startup neutralizes this class of bug — assignment to a frozen prototype becomes a silent no-op in sloppy mode or a TypeError in strict mode. Node's --frozen-intrinsics flag does this for built-ins automatically.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

June 22, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 260f9cd2ac5c (thomaspoignant/scim-patch)

Patch available: thomaspoignant/scim-patch v0.9.1 (contains commit 260f9cd2ac5c)

https://github.com/thomaspoignant/scim-patch/commit/260f9cd2ac5ceac3976978850bb47dcb391720f6
github Patch Available🟡 PoC Available

Prototype pollution in scimPatch via unfiltered keys in patch · Advisory · thomaspoignant/scim-patch · GitHub

https://github.com/thomaspoignant/scim-patch/security/advisories/GHSA-9m6g-wc8r-q59c

Vendor Advisories for CVE-2026-48170(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
scim-patch—0.9.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 22:13 UTCEG score recompute
  4. 2026-08-24 13:55 UTCEG score recompute
  5. 2026-08-23 03:23 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 14:54 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 00:38 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 07:49 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-19 04:51 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 17:04 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 20:14 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 05:18 UTCEG score recompute
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 03:20 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 22:48 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 16:26 UTCEG score recompute
Show 15 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 15:58 UTCEG score recompute
  3. 2026-08-11 03:44 UTCEG score recompute
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 15:29 UTCEG score recompute
  6. 2026-08-10 14:35 UTCEG score recompute
  7. 2026-08-09 15:21 UTCEG score recompute
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 18:57 UTCEG score recompute
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-07 22:33 UTCEG score recompute
  12. 2026-07-30 19:22 UTCEG score recompute
  13. 2026-07-26 15:56 UTCEG score recompute
  14. 2026-07-23 03:18 UTCEG score recompute
  15. 2026-06-22 23:31 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48170?
CVE-2026-48170 is a critical vulnerability published on June 22, 2026. scim-patch, a library to perform SCIM patch, prior to version 0.9.1 performs prototype pollution when applying a SCIM PATCH operation whose value object contains a key like "proto.someProp". After one such patch, Object.prototype.someProp is set process-wide, affecting every plain object in the…
When was CVE-2026-48170 disclosed?
CVE-2026-48170 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48170 actively exploited?
CVE-2026-48170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.8% of all scored CVEs.
What is the CVSS score of CVE-2026-48170?
CVE-2026-48170 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48170?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48170, 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-2026-48170

Explore →

Is Your Infrastructure Affected by CVE-2026-48170?

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

Start Free Scan →Browse All CVEs