CVE-2026-59151

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.6
EG Score
9.6(medium)
EPSS
21.5%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (5)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

Prowler 5.30.3

Patch available: prowler-cloud/prowler 5.30.3

https://github.com/prowler-cloud/prowler/releases/tag/5.30.3
github_commit

commit f5ff30ad175b (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit f5ff30ad175b — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/f5ff30ad175bd2edf02cd28872653c1cda5867b7
github_commit

commit bf3b5c2ba713 (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit bf3b5c2ba713 — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/bf3b5c2ba713e533014927141b64948c82c8f32e
github_pr

fix(saml): cross-tenant account takeover via SAML domain claiming

Fix merged in prowler-cloud/prowler PR #11650 on 2026-06-19 — awaiting tagged release

https://github.com/prowler-cloud/prowler/pull/11650
github Patch Available🟡 PoC Available

SAML Domain Claiming Enables Cross-Tenant Account Takeover · Advisory · prowler-cloud/prowler · GitHub

https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 37× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 14:55 UTCEG score recompute
  4. 2026-07-15 10:37 UTCEG score recompute
  5. 2026-07-15 06:13 UTCEG score recompute
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 01:54 UTCEG score recompute
  9. 2026-07-14 21:36 UTCEG score recompute
  10. 2026-07-14 17:17 UTCEG score recompute
  11. 2026-07-14 12:53 UTCEG score recompute
  12. 2026-07-14 08:34 UTCEG score recompute
  13. 2026-07-14 04:14 UTCEG score recompute
  14. 2026-07-13 23:56 UTCEG score recompute
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 19:38 UTCEG score recompute
  17. 2026-07-13 15:19 UTCEG score recompute
  18. 2026-07-13 10:59 UTCEG score recompute
  19. 2026-07-13 06:41 UTCEG score recompute
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 02:23 UTCEG score recompute
  23. 2026-07-12 22:05 UTCEG score recompute
  24. 2026-07-12 17:46 UTCEG score recompute
  25. 2026-07-12 13:26 UTCEG score recompute
Show 12 more
  1. 2026-07-12 09:08 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-12 04:50 UTCEG score recompute
  4. 2026-07-12 00:32 UTCEG score recompute
  5. 2026-07-11 20:14 UTCEG score recompute
  6. 2026-07-11 15:56 UTCEG score recompute
  7. 2026-07-11 11:37 UTCEG score recompute
  8. 2026-07-11 07:19 UTCEG score recompute
  9. 2026-07-11 03:00 UTCEG score recompute
  10. 2026-07-10 22:42 UTCEG score recompute
  11. 2026-07-10 18:23 UTCEG score recompute
  12. 2026-07-10 18:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59151?
CVE-2026-59151 is a critical vulnerability published on July 10, 2026. 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…
When was CVE-2026-59151 disclosed?
CVE-2026-59151 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59151 actively exploited?
CVE-2026-59151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59151?
CVE-2026-59151 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-59151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59151

Explore →

Is Your Infrastructure Affected by CVE-2026-59151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs