CVE-2026-55088Etherpad: Device-to-device author-token transfer endpoint is replayable, never expires, and exposes the cleartext author token
Updated under an hour ago ()
Does this affect you?
It affects etherpad. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
Etherpad is a real-time collaborative editor. From 2.6.0 until 3.1.0, Etherpad's src/node/hooks/express/tokenTransfer.ts uses POST /tokenTransfer to store an author token for transfer between browsers and exposes it through GET /tokenTransfer/{uuid}. Although the record includes createdAt, the transfer has no expiration check, is not removed after successful redemption, and is returned by res.send(tokenData), including the raw author token. An unauthenticated attacker who obtains a transfer UUID can repeatedly redeem it, receive fresh author cookies, read the cleartext token, and impersonate the originating author for pad read and write operations. This issue is fixed in version 3.1.0.
- CVSS
- 6.8 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-200, CWE-294
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Aug 21, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
ether etherpad ether:etherpad (from the name) | from 2.6.0, < 3.1.0 | CNA record |
References
- https://github.com/ether/etherpad/security/advisories/GHSA-vqfp-p66c-xrp9x-refsource-confirm
- https://github.com/ether/etherpad/pull/7784x-refsource-misc
- https://github.com/ether/etherpad/commit/8c6104c5d5daf41f0d454acc04d42dffa0e0d996x-refsource-misc
- https://github.com/ether/etherpad/tree/3.1.0x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.