Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-59151 critical CVSS 9.6

Authentication Bypass in prowler-cloud (CVE-2026-59151)

Summary

Authentication bypass in prowler-cloud (CVE-2026-59151). Confidential information can be exposed externally. Exploitable via POST /api/v1/accounts/saml/victim.com/acs/. Mitigation: upgrade to 5.30.3 or later.

Original description

The description as published by the source.

SAML Tenant Binding Enables Cross-Tenant Account Takeover

Summary

Prowler's SAML authentication flow trusted the email domain asserted in a SAMLResponse when deciding which tenant should receive the final token. A malicious tenant with its own SAML configuration and a self-controlled IdP could complete a valid SAML flow for its own configured domain, while asserting an email address from another configured domain.

In the vulnerable flow, the ACS finish logic later derived the tenant from the asserted email domain instead of binding token issuance to the tenant associated with the validated SAML configuration. This could cause a token to be issued for the wrong tenant.

The attacker does not generally need to claim the victim's email domain. If the victim tenant already has SAML configured for that domain, another tenant cannot claim it because SAMLConfiguration.email_domain and SAMLDomainIndex.email_domain are globally unique.

Details

The confirmed root cause is in the SAML ACS finish and token issuance flow. The flow selected a SAML configuration through the ACS route, but later recalculated the tenant from the asserted user email domain:

email_domain = user.email.split("@")[-1]
tenant = (
    SAMLConfiguration.objects.using(MainRouter.admin_db)
    .get(email_domain=email_domain)
    .tenant
)

This is unsafe because user.email is derived from the SAML assertion. The tenant used for membership updates and token issuance must come from the…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-59151 has been found in prowler-cloud.
Attackers can target a specific entry point like POST /api/v1/accounts/saml/victim.com/acs/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade prowler-cloud to 5.30.3 or later.
If unsure, ask your IT team or search "prowler-cloud CVE-2026-59151" on the vendor's site.

CVE-2026-59151 (prowler-cloud) — CWE-287 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/accounts/saml/victim.com/acs/ / POST /api/v1/saml-config. / POST /api/v1/accounts/saml/{VICTIM_DOMAIN}/acs/ / SAMLConfiguration.email_domain
Patched: 5.30.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in prowler-cloud. Attackers reach the vulnerable code path via POST /api/v1/accounts/saml/victim.com/acs/.

📍 Affected scope

Check the vendor advisory for the affected versions of prowler-cloud. Attack surface: POST /api/v1/accounts/saml/victim.com/acs/ / POST /api/v1/saml-config. / POST /api/v1/accounts/saml/{VICTIM_DOMAIN}/acs/ / SAMLConfiguration.email_domain.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.30.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v1/accounts/saml/victim.com/acs/ requests with malformed payloads or SQL meta-characters. Run grep -r 'prowler-cloud' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'prowler-cloud' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で prowler-cloud を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/v1/accounts/saml/victim.com/acs/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/accounts/saml/victim.com/acs/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade prowler-cloud to 5.30.3

    ステージング環境で 5.30.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/v1/accounts/saml/victim.com/acs/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip prowler-cloud
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.30.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details