GHSA-92hr-gmr6-h8cp Etherpad addressed weak token RNG, login timing, plugin path handling, API request handling
Not scored
Published
Check this codebase for GHSA-92hr-gmr6-h8cp and fix it if it is affected.
What it is: GHSA-92hr-gmr6-h8cp is a vulnerability in ep_etherpad-lite, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-92hr-gmr6-h8cp in the wild and no public exploit code.
Affected packages and fixed versions:
- ep_etherpad-lite (npm): affected all versions; fixed in 3.3.0
- ep_etherpad-lite (npm): affected all versions; fixed in 3.3.0
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-92hr-gmr6-h8cp/ (Markdown: https://insights.sbomify.com/GHSA-92hr-gmr6-h8cp/index.md)
Etherpad hardening fixes address weak token generation, timing attacks, path traversal, and information disclosure in API and admin interfaces.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-92hr-gmr6-h8cp?
GHSA-92hr-gmr6-h8cp is a vulnerability in ep_etherpad-lite, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Fix: PR #7906 (ether/etherpad). A set of medium/low hardening fixes:
- Weak RNG for tokens (CWE-330): author/session/readonly IDs were generated with
Math.random()(client and server). Now usecrypto.getRandomValues. - Login timing / no failure delay (CWE-208/CWE-307): the OIDC interaction login used a non-constant-time password compare with no failure delay. Now uses
crypto.timingSafeEqualplus a uniform failure delay; user lookup is own-property only. - Plugin dependency path handling (CWE-22): plugin dependency names from package.json were used to build filesystem paths without validation (admin-gated install). Now validated against the npm name grammar.
- API parameter pollution (CWE-235):
/api/2merged all request headers into the API field set. Now forwards onlyauthorization, matching the openapi.ts handler. - Pad-creation side effect:
API.appendChatMessagecould create arbitrary pads (missinggetPadSafe). Now requires the pad to exist. - Error info disclosure (CWE-209): the admin file server echoed filesystem error detail; now returns a generic message.
Which versions are affected by GHSA-92hr-gmr6-h8cp?
2 open source packages ship an affected version, including ep_etherpad-lite.
| Package | Affected | Fixed in |
|---|---|---|
ep_etherpad-lite npm | All versions | 3.3.0 |
ep_etherpad-lite npm | All versions | 3.3.0 |
How do I fix GHSA-92hr-gmr6-h8cp?
Upgrade ep_etherpad-lite to 3.3.0 or later.
Is GHSA-92hr-gmr6-h8cp being exploited?
There is no known exploitation of GHSA-92hr-gmr6-h8cp in the wild and no public exploit code.