cve.bz

CVE-2026-126570 Padloc 4.0.0 before 4.3.1 Prototype Pollution via SCIM PATCH setPath()

7.0 highEPSS 0.4%

High (7.0) in padloc padloc. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.0 high
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

CVSS 3.1

7.6 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126570 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126570?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126570?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126570 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126570

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126570](https://cve.bz/cve/badge/CVE-2026-126570.svg)](https://cve.bz/cve/CVE-2026-126570)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126570"><img src="https://cve.bz/cve/badge/CVE-2026-126570.svg" alt="CVE-2026-126570"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
padlocfrom 4.0.0 before 4.3.1

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON