Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Prowler versions before 5.30.3 are vulnerable (prowler-cloud package). In the SAML sign-in flow, the token could be issued for the tenant derived from the asserted email domain rather than the tenant whose SAML configuration was validated. An attacker who controls a tenant with its own SAML configuration and IdP could possibly obtain a token for another tenant. Upgrade to prowler-cloud 5.30.3 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.6 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N | CNA (Secur0) |
- CISA KEV Not listed.
- EPSS 0.0085, the 58th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-h8m9-jgf8-vwvp
- OSV: GHSA-h8m9-jgf8-vwvp
- github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp
- nvd.nist.gov/vuln/detail/CVE-2026-59151
- github.com/prowler-cloud/prowler/pull/11650
- github.com/prowler-cloud/prowler/commit/bf3b5c2ba713e533014927141b64948c82c8f32e
- github.com/prowler-cloud/prowler/commit/f5ff30ad175bd2edf02cd28872653c1cda5867b7
- github.com/prowler-cloud/prowler
- github.com/prowler-cloud/prowler/releases/tag/5.30.3
- github.com/pypa/advisory-database/tree/main/vulns/prowler-cloud/PYSEC-2026-3725.yaml