Coop has SAML cross-tenant authentication bypass
Affects Coop versions before 1.0.2 that use the SAML login strategy. Fixed in 1.0.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Coop, an open source review and moderation tool, is affected when its SAML single sign-on login is used across multiple organizations. An attacker who runs one organization and holds its SAML signing key could log in as a user from another organization that uses the same signing certificate, taking over that user's account without having any access in the target organization.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Coop is an open source review and moderation tool from ROOST. Prior to 1.0.2, the SAML strategy's verify callback resolved the authenticated user by email alone using `kyselyUserFindByEmail`, without binding the lookup to the organization in `/saml/login/:orgId/callback`. An attacker who administers an organization and controls its SAML IdP signing key can submit an assertion for a victim email to another organization's callback when that target organization has registered the same signing certificate. The assertion verifies against the target certificate, and the email resolves to the target user, creating a session as that user and allowing full cross-tenant account takeover without privileges in the target organization. Exploitation requires the unusual configuration in which the target certificate matches a signing key controlled by the attacker. This issue is fixed in version 1.0.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- roostorg coop
fixed in 1.0.2
References 4
GitHub · roostorg/coop
Questions about CVE-2026-63398
What does this mean?
A flaw in Coop's SAML login lets an account from one organization sign in as a user in another organization. The result is a full cross-tenant account takeover, and no privileges in the target organization are needed.Source: github.com
Am I affected, and how do I check?
The issue is in Coop versions before 1.0.2 that use the SAML login strategy. The advisory's conditions are that the target organization uses the same SAML signing certificate as the attacker's organization, and that the attacker is an admin of some organization, which is needed to register a SAML IdP. To check, look at the installed Coop version and whether SAML is the configured login strategy.Source: github.com
What should I do about it?
Upgrade Coop to version 1.0.2 or later, which is the listed fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data