PADLOC · CVE-2026-126570 · Other
NO FIX YET · SEE WHAT TO DO
Padloc 4.0.0 before 4.3.1 lets a holder of a SCIM token send crafted PATCH paths that modify Object.prototype in the shared server process. The polluted prototype disrupts requests for every other organization on that server.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Self-hosted or hosted Padloc instances on versions 4.0.0 through 4.2.x that use SCIM provisioning are exposed. The flaw needs a valid SCIM token, so instances without SCIM enabled or without issued tokens are not exposed. Any organization on a shared server can be disrupted by a token holder from another organization.
Not affected if patched-4.3.1, scim-disabled
Who cares padloc, scim, self-hosted
4.0.0 up to but not including 4.3.1.4.3.1 or later.Padloc 4.0.0 before 4.3.1 contains a prototype pollution vulnerability that allows SCIM token holders to modify Object.prototype by sending crafted SCIM PATCH paths to ScimServer._handleScimUsersPatch(). Attackers can supply paths like proto.x or constructor.prototype.x passed to setPath() to pollute the shared server process, disrupting requests for all other organizations.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.