vulns.co
/
GKData.io MCP and API Buy me a coffee

Prowler

Prowler SAML: retain validated tenant authority

Prowler's maintainers report that token issuance chose a tenant from an asserted email domain rather than the validated SAML configuration (CVE-2026-59151). They describe possible cross-tenant account takeover. Their adapter-level demonstration showed a linking-method call, not a persisted account link, completed token issuance or production compromise.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Keep federation configuration, accepted identity claims, membership changes and issued-token tenant consistent. The advisory lists Prowler API through 5.30.2 as affected and 5.30.3 as patched; no patch-release date is established here.

Before reading

  • Basic federation and object-level authorization concepts

Context and limits

  • Requires SAML, authenticated control of a tenant configuration and identity provider, and a target domain mapped to another SAML tenant; no victim interaction.
  • Configured domains remain globally unique. The advisory narrative corrects conflicting older demonstration comments.
  • Credits: EQSTLab, reporter; AdriiiPRodri, remediation developer; jfagoagas, coordinator/publishing account; josema-xyz, analyst. Article authorship is not established.
  • Broader access and persistence are potential consequences. The fix was not independently audited.
  • The displayed test mocks the linking method and checks its invocation with an existing user; it is narrower evidence than completed persistent linking.

Sources

  1. SAML Domain Claiming Enables Cross-Tenant Account TakeoverProwler · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software