Coop has SAML cross-tenant authentication bypass
Impact
Coop, an open-source review tool, has a SAML authentication bypass vulnerability in versions prior to 1.0.2. An attacker with control over an organization's SAML IdP signing key can take over another organization's account. This requires a specific configuration where the target certificate matches the attacker's signing key.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Exploitation requires the unusual configuration in which the target certificate matches a signing key controlled by the attacker.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
roostorg · GitHub_M
coop
1 range
roostorg · GitHub_M
coop
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 1.0.2
Other versions: unknown
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-63398View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.