CVE-2026-48170

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-22. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-54686 (ENISA EUVD) · GHSA-9m6g-wc8r-q59c (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 22, 2026

Last Modified

October 23, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmscim-patch @ 0.9.1 (fixes <= 0.9.0)—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)
PackageVulnerable rangeFix by version rangeDependents
scim-patch—
  • every version up to 0.9.1: fixed in 0.9.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 60× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 128 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 28 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 10:38 UTCEG score recompute
  2. 2026-11-02 10:38 UTCGHSA enrichmentGHSA-9m6g-wc8r-q59c · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-11-01 11:41 UTCGHSA enrichmentGHSA-9m6g-wc8r-q59c · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-11-01 07:47 UTCGHSA enrichmentGHSA-9m6g-wc8r-q59c · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-01 07:47 UTCEG score recompute
  7. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-31 12:44 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-30 13:48 UTCEG score recompute
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-29 14:45 UTCEG score recompute
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-27 16:52 UTCEG score recompute
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-26 17:55 UTCEG score recompute
  17. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-25 18:25 UTCEG score recompute
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-25 14:23 UTCEG score recompute
  21. 2026-10-24 19:23 UTCEG score recompute
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-23 20:27 UTCEG score recompute
  24. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-23 09:12 UTCEG score recompute
Show 75 more
  1. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-22 10:15 UTCEG score recompute
  3. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-21 11:16 UTCEG score recompute
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-20 12:19 UTCEG score recompute
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-19 13:15 UTCEG score recompute
  9. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-18 03:35 UTCEG score recompute
  11. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-17 13:24 UTCEG score recompute
  13. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-16 14:26 UTCEG score recompute
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-15 14:39 UTCEG score recompute
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-14 09:14 UTCEG score recompute
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-13 06:24 UTCEG score recompute
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-12 16:01 UTCEG score recompute
  23. 2026-10-11 19:44 UTCEG score recompute
  24. 2026-10-11 16:58 UTCEG score recompute
  25. 2026-10-11 14:23 UTCEG score recompute
  26. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  29. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-10-08 14:54 UTCOSV refresh
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  32. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  39. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  40. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  43. 2026-09-18 20:36 UTCEG score recompute
  44. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  45. 2026-09-18 11:12 UTCEG score recompute
  46. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  47. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  48. 2026-09-14 02:07 UTCEG score recompute
  49. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  50. 2026-09-13 12:29 UTCEG score recompute
  51. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  52. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  53. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  54. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  55. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  56. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  57. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  58. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  59. 2026-08-30 20:30 UTCEG score recompute
  60. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  61. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  62. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  63. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  64. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  65. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  66. 2026-08-24 22:13 UTCEG score recompute
  67. 2026-08-24 13:55 UTCEG score recompute
  68. 2026-08-23 03:23 UTCEG score recompute
  69. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  70. 2026-08-22 14:54 UTCEG score recompute
  71. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  72. 2026-08-21 00:38 UTCEG score recompute
  73. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  74. 2026-08-20 07:49 UTCEG score recompute
  75. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 16th percentile

Related CVEs(same product + same CWE)

Same product

1 shown

npm:scim-patch

Frequently asked(5)

What is CVE-2026-48170?
CVE-2026-48170 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-48170 published?
The CVE record for CVE-2026-48170 was published on June 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-48170 actively exploited?
CVE-2026-48170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48170?
CVE-2026-48170 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48170?
A fix for CVE-2026-48170 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48170 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs