Is CVE-2026-63400 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63400 being exploited in the wild.

How severe is CVE-2026-63400?

Informational severity, published 30 October 2026.

Is there a fix for CVE-2026-63400?

Yes: fixed in 1.0.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63400 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-63400?

Check whether you run ROOST Coop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63400: ROOST Coop session fixation on password reset

CVE-2026-63400 · Severity: info · Published 2026-10-30

Coop is an open-source review and moderation tool. When a user resets their password via email, the password is updated but the attacker's existing session remains valid for up to 30 days, allowing an attacker who has compromised an account to retain access even after the legitimate user takes recovery action. An attacker must already have obtained valid login credentials and established a session to exploit this.

Technologies: ROOST Coop. Vendors: ROOST.

Quick answers

Is CVE-2026-63400 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63400 being exploited in the wild.
How severe is CVE-2026-63400?: Informational severity, published 30 October 2026.
Which products and versions are affected?: ROOST Coop prior to 1.0.2.
Is there a fix for CVE-2026-63400?: Yes: fixed in 1.0.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63400 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-63400?: Check whether you run ROOST Coop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.0.2

Technical details

The `resetPasswordForToken` function failed to invalidate database-backed sessions (via connect-pg-simple with a 30-day maxAge) when a password was reset. Because Passport's deserializeUser looks up users by ID only, a compromised session persists after password reset until natural session expiration. The fix adds `deleteSessionsForUser()` to remove all session rows from the database during both password change and password reset, wrapped in a transaction to ensure atomicity.

Affected products

ROOST Coop prior to 1.0.2

Timeline

2026-10-30: disclosed
2026-06-16: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.