{"answers":{"affected":"2 open source packages ship an affected version, including scim-patch.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48170 exists.","fix":"Upgrade scim-patch to 0.9.1 or later.","what":"CVE-2026-48170 is a critical code injection vulnerability in thomaspoignant scim-patch, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48170 and fix it if it is affected.\n\nWhat it is: CVE-2026-48170 is a critical code injection vulnerability in thomaspoignant scim-patch, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48170 exists.\n\nAffected packages and fixed versions:\n- scim-patch (npm): affected all versions; fixed in 0.9.1\n- scim-patch (npm): affected all versions; fixed in 0.9.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48170/ (Markdown: https://insights.sbomify.com/CVE-2026-48170/index.md)","id":"CVE-2026-48170","markdown":"https://insights.sbomify.com/CVE-2026-48170/index.md","name":"CVE-2026-48170","record":{"aliases":["GHSA-9m6g-wc8r-q59c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"SCIM patch library","requires_auth":"low_privilege","summary":"Prototype pollution in scim-patch allows attackers to modify Object.prototype via crafted SCIM PATCH requests, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"`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,\n`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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"scimPatch vulnerable to prototype pollution via unfiltered keys in patch","id":"CVE-2026-48170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"LiteSpeed cPanel Plugin Privilege Escalation","id":"CVE-2026-48172"},"packages":[{"ecosystem":"npm","fixed":["0.9.1"],"introduced":["0"],"last_affected":[],"package":"scim-patch","purl":null,"source":"GHSA-9m6g-wc8r-q59c"},{"ecosystem":"npm","fixed":["0.9.1"],"introduced":["0"],"last_affected":[],"package":"scim-patch","purl":"pkg:npm/scim-patch","source":"GHSA-9m6g-wc8r-q59c"}],"prev":{"headline":"PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API","id":"CVE-2026-48169"},"products":["scim-patch"],"published":"2026-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["thomaspoignant"]},"summary":"Prototype pollution in scim-patch allows attackers to modify Object.prototype via crafted SCIM PATCH requests, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-48170/"}