Vulnerabilities in pkg:npm/scim-patch

PACKAGE
Advisory Identifier: GHSA-2mhw-wcx5-v3xj
Advisory Summary

CVE-2026-61834 is a MODERATE (CVSS 4.3) mutation of inherited built-in method vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting scim-patch libraries in the npm ecosystem. The issue involves mutation of inherited built-in method objects. Remediation is available by upgrading affected packages to version 0.9.2.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/scim-patch

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/scim-patch. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-2mhw-wcx5-v3xj CVE-2026-61834 MODERATE scim-patch: Mutation of Inherited Built-in Method Objects
GHSA-9m6g-wc8r-q59c CVE-2026-48170 CRITICAL scimPatch vulnerable to prototype pollution via unfiltered keys in patch

CVE-2026-61834 at a Glance

CVE Identifier CVE-2026-61834
GHSA Identifier GHSA-2mhw-wcx5-v3xj
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Affected Product scim-patch
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-61834

To remediate this vulnerability, upgrade all affected scim-patch dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

scim-patch fixed: 0.9.2
npm install scim-patch@0.9.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls scim-patch

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-61834, inspect your project dependencies using npm:

npm ls scim-patch

Analyze the terminal output to locate any version of scim-patch in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.9.2), your application is affected.

Note: The npm ls scim-patch command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), where the product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. In scim-patch, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Incomplete Prototype Pollution Fix Allows Mutation of Inherited Built-in Method Objects `scim-patch` blocks direct dangerous path segments such as `__proto__`, `constructor`, and `prototype`, but still traverses inherited properties when applying SCIM patch paths. An attacker who controls a SCIM PATCH operation can use paths such as `toString.polluted` to mutate shared built-in function objects, for example `Object.prototype.toString`. ## Impact A malicious patch can add attacker-controlled properties to inherited built-in method objects. The impact is narrower than direct `Object.prototype` pollution, but the mutation is process-global and may affect application logic that reads properties from inherited methods. ## Details Affected code paths: - `navigate()` reads inherited properties via `schema[subPath]` - `assign()` uses `key in obj`, which treats inherited properties as existing Because inherited keys are followed, safe-looking path segments such as `toString` can resolve to shared built-in objects. ## PoC ```js const assert = require("node:assert/strict"); const { scimPatch } = require("./lib/src/scimPatch"); const victim = { schemas: ["urn:ietf:params:scim:schemas:core:2.0:User"], userName: "alice", active: true, emails: [{ value: "alice@example.com", primary: true }], meta: { created: "x", lastModified: "x", resourceType: "User" } }; try { assert.equal(({}).toString.scimPatchPolluted, undefined); scimPatch(victim, [ { op: "add", path: "toString.scimPatchPolluted", value: "polluted" } ]); assert.equal(({}).toString.scimPatchPolluted, "polluted"); console.log(({}).toString.scimPatchPolluted); } finally { delete Object.prototype.toString.scimPatchPolluted; } ``` Output: ```text polluted ``` A no-path operation with a dotted value key is also affected: ```js scimPatch(victim, [ { op: "add", value: { "toString.noPathPolluted": "polluted" } } ]); ``` ## Remediation Do not traverse inherited properties while resolving patch paths. Use own-property checks such as `Object.hasOwn(obj, key)` and create missing containers only for safe own keys. Keep the existing denylist for `__proto__`, `constructor`, and `prototype` as defense in depth.

CVE-2026-61834 Affected scim-patch Versions

1 component(s)
Fixed Versions:
0.9.2
Product / Package Ecosystem Affected Versions Fixed Version
scim-patch
npm
< 0.9.2
0.9.2

References

Frequently Asked Questions

What is CVE-2026-61834?
CVE-2026-61834 is a security vulnerability in scim-patch involving Mutation of Inherited Built-in Method Objects under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
Which scim-patch versions are affected?
Affected versions include releases prior to 0.9.2 across affected packages: scim-patch.
What version fixes CVE-2026-61834?
Upgrading to 0.9.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is scim-patch affected?
Yes, scim-patch is affected in releases prior to 0.9.2. Upgrade your dependency to 0.9.2 or later.
What is the CVSS score of CVE-2026-61834?
CVE-2026-61834 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-61834?
CVE-2026-61834 is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.).
How can I check npm dependencies for CVE-2026-61834?
Run the dependency tree command: 'npm ls scim-patch'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2mhw-wcx5-v3xj",
  "modified" : "2026-09-28T14:01:15Z",
  "published" : "2026-09-28T14:01:15Z",
  "aliases" : [ "CVE-2026-61834" ],
  "summary" : "scim-patch: Mutation of Inherited Built-in Method Objects",
  "details" : "## Summary\n\nIncomplete Prototype Pollution Fix Allows Mutation of Inherited Built-in Method Objects\n\n`scim-patch` blocks direct dangerous path segments such as `__proto__`, `constructor`, and `prototype`, but still traverses inherited properties when applying SCIM patch paths.\n\nAn attacker who controls a SCIM PATCH operation can use paths such as `toString.polluted` to mutate shared built-in function objects, for example `Object.prototype.toString`.\n\n## Impact\n\nA malicious patch can add attacker-controlled properties to inherited built-in method objects. The impact is narrower than direct `Object.prototype` pollution, but the mutation is process-global and may affect application logic that reads properties from inherited methods.\n\n## Details\n\nAffected code paths:\n\n- `navigate()` reads inherited properties via `schema[subPath]`\n- `assign()` uses `key in obj`, which treats inherited properties as existing\n\nBecause inherited keys are followed, safe-looking path segments such as `toString` can resolve to shared built-in objects.\n\n## PoC\n\n```js\nconst assert = require(\"node:assert/strict\");\nconst { scimPatch } = require(\"./lib/src/scimPatch\");\n\nconst victim = {\n  schemas: [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  userName: \"alice\",\n  active: true,\n  emails: [{ value: \"alice@example.com\", primary: true }],\n  meta: { created: \"x\", lastModified: \"x\", resourceType: \"User\" }\n};\n\ntry {\n  assert.equal(({}).toString.scimPatchPolluted, undefined);\n\n  scimPatch(victim, [\n    { op: \"add\", path: \"toString.scimPatchPolluted\", value: \"polluted\" }\n  ]);\n\n  assert.equal(({}).toString.scimPatchPolluted, \"polluted\");\n  console.log(({}).toString.scimPatchPolluted);\n} finally {\n  delete Object.prototype.toString.scimPatchPolluted;\n}\n```\n\nOutput:\n\n```text\npolluted\n```\n\nA no-path operation with a dotted value key is also affected:\n\n```js\nscimPatch(victim, [\n  { op: \"add\", value: { \"toString.noPathPolluted\": \"polluted\" } }\n]);\n```\n\n## Remediation\n\nDo not traverse inherited properties while resolving patch paths. Use own-property checks such as `Object.hasOwn(obj, key)` and create missing containers only for safe own keys.\n\nKeep the existing denylist for `__proto__`, `constructor`, and `prototype` as defense in depth.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "scim-patch"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.9.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/thomaspoignant/scim-patch/security/advisories/GHSA-2mhw-wcx5-v3xj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-61834"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/thomaspoignant/scim-patch/pull/1127"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/thomaspoignant/scim-patch/commit/c86474f7a9b16191d939f59ba94eca6c6e63044b"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/thomaspoignant/scim-patch"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/thomaspoignant/scim-patch/releases/tag/v0.9.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1321", "CWE-915" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-28T14:01:15Z",
    "nvd_published_at" : "2026-09-23T15:17:15Z"
  }
}