How severe is GHSA-92hr-gmr6-h8cp?

No CVSS score has been assigned to GHSA-92hr-gmr6-h8cp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-92hr-gmr6-h8cp?

GHSA-92hr-gmr6-h8cp affects the following packages: ep_etherpad-lite (npm). Ecosystems affected: npm.

How do I fix GHSA-92hr-gmr6-h8cp?

Update ep_etherpad-lite to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92hr-gmr6-h8cp is resolved across your whole dependency graph.

How do I detect GHSA-92hr-gmr6-h8cp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ep_etherpad-lite. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-92hr-gmr6-h8cp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-92hr-gmr6-h8cp?

O3 pinpoints whether GHSA-92hr-gmr6-h8cp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-92hr-gmr6-h8cp actively exploited in the wild?

No public exploit code has been indexed for GHSA-92hr-gmr6-h8cp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-92hr-gmr6-h8cp published, and has it been updated?

GHSA-92hr-gmr6-h8cp was published on August 17, 2026 and was last updated on August 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-92hr-gmr6-h8cp

Fix: ether/etherpad#7906

GHSA-92hr-gmr6-h8cp is a security vulnerability in ep_etherpad-lite. O3 Security confirms whether GHSA-92hr-gmr6-h8cp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Published

Aug 17, 2026

Updated

Aug 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 17, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

ep_etherpad-litenpm

253downloads / week

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 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 admin file server echoed filesystem error detail; now returns a generic message.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ep_etherpad-lite`	all versions	3.3.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ep_etherpad-lite. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ep_etherpad-lite to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92hr-gmr6-h8cp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-92hr-gmr6-h8cp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-92hr-gmr6-h8cp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 w

O3 Security · Impact-Aware SCA

Is GHSA-92hr-gmr6-h8cp in your dependencies?

O3 detects GHSA-92hr-gmr6-h8cp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works