dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-59151

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Prowler's SAML authentication flow incorrectly recalculated tenant from user.email instead of binding token issuance to the validated SAML configuration. An attacker with a controlled SAML IdP could assert an email from a different configured tenant's domain during authentication, causing the system to issue a SAMLToken and tenant-scoped JWT for the wrong tenant, enabling cross-tenant account takeover.

MitigationUpgrade Prowler to version 5.30.3 or later. If unable to upgrade immediately, review SAML IdP configurations to ensure only trusted IdPs are permitted and implement additional logging to detect anomalous tenant assignments during SAML authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Prowler version
    Run 'prowler --version' or check the installed package version (pip show prowler) to compare against version 5.30.3
    Affected if Installed version is lower than 5.30.3
  2. Confirm SAML authentication is enabled
    Inspect Prowler configuration for SAML-related settings (environment variables PROWLER_SAML_*, config file with SAML IdP settings, or authentication method in use)
    Affected if SAML authentication is configured and active
  3. Verify multi-tenant configuration exists
    Review tenant configuration files or environment variables that define multiple tenant domains (such as PROWLER_TENANT_* settings or tenant-specific email domain mappings)
    Affected if More than one tenant with different email domains is configured
  4. Review SAML IdP metadata for tenant assignment logic
    Examine the SAML IdP configuration or metadata to confirm it can assert email addresses from domains belonging to different configured tenants
    Affected if SAML IdP can assert emails from multiple tenant domains

You are affected if Prowler version is below 5.30.3 AND SAML authentication is enabled with multiple tenants configured across different email domains

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Prowler to version 5.30.3 or later. If unable to upgrade immediately, review SAML IdP configurations to ensure only trusted IdPs are permitted and implement additional logging to detect anomalous tenant assignments during SAML authentication.

Recommended fix High confidence

5.30.3

  1. Identify the current Prowler installation method (pip, docker, or git clone)
  2. Check the currently installed version using 'prowler --version' or 'pip show prowler'
  3. For pip installations: run 'pip install --upgrade prowler' to upgrade to the latest version
  4. For docker: pull the latest image with 'docker pull prowlercloud/prowler:latest' and redeploy
  5. For git installations: run 'git fetch --all' followed by 'git checkout <tag>' for version 5.30.3 or later, or 'git pull' if on a branch
  6. Verify the upgrade was successful by checking 'prowler --version' shows 5.30.3 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,500
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59151 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data