Vulnerability in scim-patch (CVE-2026-48170)
Summary
Vulnerability in scim-patch (CVE-2026-48170). Data can be tampered with by attackers. Exploitable via PATCH /Users/. Mitigation: upgrade to 0.9.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48170 has been found in scim-patch.
Attackers can target a specific entry point like PATCH /Users/ over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade scim-patch to 0.9.1 or later.
If unsure, ask your IT team or search "scim-patch CVE-2026-48170" on the vendor's site.
CVE-2026-48170 (scim-patch) — CWE-1321 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /Users/ / value / Object.prototype.someProp / PATCH
Patched: 0.9.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in scim-patch. Attackers reach the vulnerable code path via PATCH /Users/.
Check the vendor advisory for the affected versions of scim-patch. Attack surface: PATCH /Users/ / value / Object.prototype.someProp / PATCH.
Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.
Update to 0.9.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /Users/ requests with malformed payloads or SQL meta-characters. Run grep -r 'scim-patch' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'scim-patch' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
scim-patchを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PATCH /Users/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /Users/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade scim-patch to 0.9.1ステージング環境で 0.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PATCH /Users/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com