Prowler is a cloud security platform. Prior to 5.30.3, Prowler's SAML authentication flow trusted the email domain asserted in a SAMLResponse when deciding which tenant should receive the final token, and the ACS finish logic in api/src/backend/api/v1/views.py recalculated the tenant from user.email instead of binding token issuance to the validated SAML configuration. An authenticated attacker with a controlled SAML IdP could complete a valid SAML flow for an attacker-controlled domain while asserting an email address from another configured domain, causing a SAMLToken and tenant-scoped JWT to be issued for the wrong tenant and enabling cross-tenant account takeover. This issue is fixed in version 5.30.3.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://github.com/prowler-cloud/prowler/commit/bf3b5c2ba713e533014927141b64948c82c8f32e Patch
- https://github.com/prowler-cloud/prowler/commit/f5ff30ad175bd2edf02cd28872653c1cda5867b7 Patch
- https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp Exploit, Vendor Advisory
- https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.6 · prowlerNVD modified 2026-10-25 15:10
Affected (CPE criteria) 1
cpe:2.3:a:prowler:prowler:*:*:*:*:*:*:*:*
References 6
- https://github.com/prowler-cloud/prowler/commit/bf3b5c2ba713e533014927141b64948c82c8f32e Patch
- https://github.com/prowler-cloud/prowler/commit/f5ff30ad175bd2edf02cd28872653c1cda5867b7 Patch
- https://github.com/prowler-cloud/prowler/pull/11650 Issue Tracking
- https://github.com/prowler-cloud/prowler/releases/tag/5.30.3 Release Notes
- https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp Exploit, Vendor Advisory
- https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp Exploit, Vendor Advisory