Information Disclosure in ep_etherpad-lite (CVE-2026-55088)
Summary
Vulnerability in ep_etherpad-lite (CVE-2026-55088). Confidential information can be exposed externally. Exploitable via prefsHttp. Mitigation: upgrade to 3.1.0 or later.
Original description
The description as published by the source.
Etherpad's device-to-device author-token transfer endpoint is replayable, never expires, and exposes the cleartext author token in the GET response body
Description
Etherpad ships an endpoint pair under /tokenTransfer (src/node/hooks/express/tokenTransfer.ts) that lets a logged-in user move their HttpOnly author token to a different browser (typically by scanning a QR code containing the transfer URL). The flow is:
- POST
/tokenTransfer— the source device sends a request whose own author cookie is read off the server-side cookie jar. The server mints a random UUID and stores the author token (and arbitraryprefsHttpfield) under a DB key keyed by that UUID. The UUID is returned. - GET
/tokenTransfer/{uuid}— the destination device GETs the URL containing the UUID. The server reads the stored record and sets the HttpOnly author cookie on the response.
The original implementation has three serious flaws:
- No expiration check.
createdAtis written to the record on POST but never inspected on GET. A leaked transfer URL is redeemable indefinitely. - No single-use enforcement. The DB record is not deleted after a successful GET, so the same URL can be redeemed repeatedly — each redemption yielding a fresh cookie set on whoever issued the GET.
- Author token echoed in the response body. The GET handler ends with
res.send(tokenData), which serializes the full record — including the raw author token — into the JSON response. Any JavaScr…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55088 has been found in ep_etherpad-lite.
Attackers can target a specific entry point like prefsHttp over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade ep_etherpad-lite to 3.1.0 or later.
If unsure, ask your IT team or search "ep_etherpad-lite CVE-2026-55088" on the vendor's site.
CVE-2026-55088 (ep_etherpad-lite) — CWE-200 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: prefsHttp / createdAt / develop / TRANSFER_TTL_MS
Patched: 3.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in ep_etherpad-lite. Attackers reach the vulnerable code path via prefsHttp without authentication.
Check the vendor advisory for the affected versions of ep_etherpad-lite. Attack surface: prefsHttp / createdAt / develop / TRANSFER_TTL_MS.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 3.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ep_etherpad-lite' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ep_etherpad-lite' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ep_etherpad-liteを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ep_etherpad-lite to 3.1.0ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com