Skip to main content
VulnerabilityPublished

CVE-2026-126570: padloc · Prototype Pollution

Affects padlocSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 4.3.1 soon.

Data as of 11 Nov 2026, 02:48 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.0
CNA (VulnCheck)CVSS 3.17.6
Patch
Available – fixed in 4.3.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade padloc to 4.3.1.

Affected software

ProductAffectedFixed in
padlocpadlocAffected
  • >=4.0.0 <4.3.1
Fixed in
  • 4.3.1
GitHubpadlocpkg:github/padlocOther threatsAffected
  • >=4.0.0 <4.3.1
Fixed in
  • 4.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Padloc to version 4.3.1 or later, where this prototype pollution vulnerability is fixed. No other mitigations are specified or required.

Description

Padloc versions 4.0.0 through 4.3.0 contain a prototype pollution vulnerability that allows SCIM token holders to modify the Object.prototype. This occurs via crafted SCIM PATCH requests to the ScimServer._handleScimUsersPatch() function, enabling attackers to inject properties into the shared server process and disrupt requests for all organizations. The vulnerability is fixed in version 4.3.1.

References

Community reviews

Loading reviews…