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 75% 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
Elevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: Elevated riskExposed: 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)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

July 10, 2026

Last Modified

August 26, 2026

Advisory Details (5)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
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
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_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_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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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-08-30 06:24 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 21:41 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 19:42 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 14:44 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 20:15 UTCEG score recompute
  11. 2026-08-24 09:49 UTCEG score recompute
  12. 2026-08-23 03:40 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 01:38 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 23:49 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 01:32 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 20:35 UTCEG score recompute
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 17:06 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 19:35 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 70 more
  1. 2026-08-16 06:13 UTCEG score recompute
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 04:25 UTCEG score recompute
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-13 22:18 UTCEG score recompute
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-12 16:07 UTCEG score recompute
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-11 13:46 UTCEG score recompute
  10. 2026-08-11 00:52 UTCEG score recompute
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-09 14:27 UTCEG score recompute
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-08 16:57 UTCEG score recompute
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-07 19:26 UTCEG score recompute
  17. 2026-08-06 17:38 UTCEG score recompute
  18. 2026-08-06 13:47 UTCEPSS rescore
  19. 2026-08-05 20:07 UTCEG score recompute
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 18:12 UTCEG score recompute
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 13:34 UTCEG score recompute
  24. 2026-08-04 10:39 UTCEPSS rescore
  25. 2026-08-03 12:54 UTCEG score recompute
  26. 2026-08-03 10:36 UTCEPSS rescore
  27. 2026-08-02 03:31 UTCEG score recompute
  28. 2026-08-02 02:27 UTCEPSS rescore
  29. 2026-08-01 05:59 UTCEG score recompute
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 19:10 UTCEG score recompute
  32. 2026-07-30 16:28 UTCEPSS rescore
  33. 2026-07-30 10:19 UTCEG score recompute
  34. 2026-07-30 01:42 UTCEG score recompute
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-30 01:30 UTCEPSS rescore
  37. 2026-07-28 18:05 UTCEG score recompute
  38. 2026-07-28 15:37 UTCEPSS rescore
  39. 2026-07-27 15:32 UTCEG score recompute
  40. 2026-07-27 14:14 UTCEPSS rescore
  41. 2026-07-26 16:28 UTCEG score recompute
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-26 12:09 UTCEG score recompute
  45. 2026-07-25 14:18 UTCEPSS rescore
  46. 2026-07-25 14:18 UTCEPSS rescore
  47. 2026-07-24 14:18 UTCEPSS rescore
  48. 2026-07-24 14:18 UTCEPSS rescore
  49. 2026-07-23 14:18 UTCEPSS rescore
  50. 2026-07-23 14:18 UTCEPSS rescore
  51. 2026-07-23 03:21 UTCEG score recompute
  52. 2026-07-22 14:08 UTCEPSS rescore
  53. 2026-07-22 14:08 UTCEPSS rescore
  54. 2026-07-21 15:25 UTCEPSS rescore
  55. 2026-07-21 15:25 UTCEPSS rescore
  56. 2026-07-20 17:08 UTCEPSS rescore
  57. 2026-07-19 14:31 UTCEPSS rescore
  58. 2026-07-19 02:29 UTCEPSS rescore
  59. 2026-07-18 10:04 UTCEPSS rescore
  60. 2026-07-16 17:03 UTCEPSS rescore
  61. 2026-07-15 16:57 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 02:00 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-13 22:31 UTCEPSS rescore
  66. 2026-07-13 06:13 UTCEPSS rescore
  67. 2026-07-13 06:13 UTCEPSS rescore
  68. 2026-07-12 05:46 UTCEPSS rescore
  69. 2026-07-10 18:23 UTCEG score recompute
  70. 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 August 26, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
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