CVE-2026-121454: Padloc through 4.3.0 Missing SCIM Token Validation via SCIM GET Requests
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Padloc through 4.3.0 contains a missing authentication vulnerability in ScimServer._handleScimGet() that allows unauthenticated attackers to read SCIM directories by sending any non-empty bearer token. Attackers who know an organization id can query the Users and Groups SCIM endpoints to retrieve provisioned usernames, emails, names, externalIds, and group memberships.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-11-03).
Weakness: Missing Authentication for Critical Function
How it can be exploited
Exploitable over the network with low attack complexity only when specific conditions are present needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 5 references on Exploit Observer
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| padloc | up to and including 4.3.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- Fix commit (patch)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-121454 Padloc - Unauthenticated SCIM Directory Disclosure. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-121454 Padloc - Unauthenticated SCIM Directory Disclosure"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/Users"; nocase; fast_pattern; pcre:"/^\/[^\/]+\/(Users|Groups)(\/[^\/]+)?$/i"; http.header; content:"Authorization|3a 20|Bearer "; nocase; classtype:web-application-attack; reference:cve,CVE-2026-121454; reference:url,https://www.exploit.observer/?keyword=CVE-2026-121454&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=padloc&match=exact; sid:1103006; rev:1;)
CVE-2026-121454.rules on GitHub
References
Vendor advisories and patches
- Fix commit (patch)
Technical analysis and advisories
- GitHub Issue #795 (issue-tracking)
- https://github.com/padloc/padloc/blob/v4.3.0/packages/server/src/scim.ts#L702-L714 (technical-description)
- VulnCheck Advisory: Padloc through 4.3.0 Missing SCIM Token Validation via SCIM GET Requests (third-party-advisory)
Other references
- https://github.com/padloc/padloc (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
