CVE-2026-55089: Etherpad: JWT `admin` claim presence-only check lets non-admin OAuth users invoke every Etherpad HTTP API endpoint
Etherpad is a real-time collaborative editor. From 2.1.0 until 3.1.0, Etherpad's src/node/handler/APIHandler.ts authorizes requests to /api/2/* in the authorization_code OAuth path by using requiredClaims with the admin claim. This check requires only that the claim exists, while src/node/security/OAuth2Provider.ts issues admin: false for configured non-admin users. A non-admin user with a valid signed token can therefore invoke administrative functions including setHTML, setText, appendText, deletePad, copyPad, movePad, restoreRevision, anonymizeAuthor, listAllPads, and listAuthorsOfPad, allowing disclosure, modification, or deletion of pads across the instance. This issue is fixed in version 3.1.0.
Security readout for executives and security teams
Plain-English summary
A signed-in, non-admin Etherpad user can be treated as an administrator because the system checks whether an `admin` claim exists, not whether it is true. This can expose, alter, move, or delete pads across the instance without administrator privileges.
Executive priority
Treat this as an urgent upgrade for affected OAuth-enabled instances. A legitimate low-privilege account could compromise the confidentiality and integrity of collaborative content across the service, with potential deletion or disruption. Investigate suspicious non-admin API activity alongside remediation.
Technical view
Etherpad 2.1.0 through versions before 3.1.0 improperly authorizes `/api/2/*` requests in the OAuth authorization-code path. Tokens issued to configured non-admin users contain `admin: false`, but the required-claim check accepts the claim's presence. This is CWE-863 improper authorization and is fixed in 3.1.0.
Likely exposure
Exposure requires an affected Etherpad version, the OAuth authorization-code path, and a configured non-admin user able to obtain a valid signed token. Internet-accessible or broadly accessible instances face greater practical risk because the flaw reaches administrative API functions across the instance.
Exploitation context
The vulnerability is network-accessible, requires low privileges, needs no user interaction, and has a CVSS 3.1 score of 9.9. The supplied record is not in KEV, and the source bundle provides no evidence of active exploitation or a public exploit.
Researcher notes
The authorization boundary fails because claim presence is confused with claim value. The provider deliberately issues `admin: false`, making affected non-admin tokens relevant. The referenced fix changes this behavior; the supplied evidence does not establish active exploitation or provide confirmed indicators of compromise.
Mitigation direction
Upgrade affected Etherpad deployments to version 3.1.0, which contains the fix.
Review the vendor advisory and release notes for deployment-specific upgrade guidance.
Prioritize instances exposing OAuth and `/api/2/*` access to untrusted or numerous users.
Validation and detection
Inventory Etherpad versions and identify deployments from 2.1.0 through versions before 3.1.0.
Determine whether the OAuth authorization-code path and configured non-admin users are present.
After upgrading, verify tokens with `admin: false` cannot invoke administrator-only API functions.
Review `/api/2/*` logs for unexpected administrative calls associated with non-admin identities.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.