Etherpad addressed weak token RNG, login timing, plugin path handling, API request handling

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 use crypto.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.timingSafeEqual plus 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/2 merged all request headers into the API field set. Now forwards only authorization, matching the openapi.ts handler. - Pad-creation side effect: API.appendChatMessage could create arbitrary pads (missing getPadSafe). Now requires the pad to exist. - Error info disclosure (CWE-209): the…

Published by the source

17 Aug 2026, 17:49 UTC

Last modified by the source

17 Aug 2026, 17:49 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-92hr-gmr6-h8cp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-92hr-gmr6-h8cp

Advisory: Etherpad addressed weak token RNG, login timing, plugin path handling, API request handling
IDs: GHSA-92hr-gmr6-h8cp
Record: https://patchnext.com/advisories/ghsa-92hr-gmr6-h8cp (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ep_etherpad-lite 3.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ep_etherpad-lite: affected <= 1.8.14; fixed in 3.3.0

## Suggested inspection (read-only)
- `npm ls ep_etherpad-lite --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ep_etherpad-lite.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-92hr-gmr6-h8cp (GitHub-reviewed advisory GHSA-92hr-gmr6-h8cp lists affected ranges: npm ep_etherpad-lite >=0 <=1.8.14)

Commands are suggestions: review each one before running it.