fix(deps): update toniblyx/prowler docker tag to v5.39.1

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Update	Change
toniblyx/prowler	minor	5.2.0 → 5.39.1

---

Release Notes

prowler-cloud/prowler (toniblyx/prowler)

v5.39.1: Prowler 5.39.1

Compare Source

API

🔄 Changed

• Bump alibabacloud-tea-openapi to 0.4.6, oci to 2.184.1 and pyopenssl to 26.4.0 to match the SDK; the cryptography override now names its actual blockers (azure-cli-core pins msal below 1.37, workos 8.3.0 requires cryptography 48) (#​12477)

🐞 Fixed

• Pin zstd to 1.5.7.2; 1.5.7.3 was yanked from PyPI as not thread safe (#​12477)

🔐 Security

• Trivy from v0.72.0 to v0.73.0 in the container image, fixing HIGH CVE-2026-46600 in the bundled golang.org/x/net (#​12445)
• Trivy v0.74.0 and Debian util-linux 2.41.5-0+deb13u1 in the API container image, patching Go standard library vulnerabilities and CVE-2026-53615 (#​12470)

SDK

🐞 Fixed

• Bump alibabacloud-tea-openapi to 0.4.6, oci to 2.184.1 and pyopenssl to 26.4.0 so the published wheel installs with cryptography 50.0.0; 5.38.0 declared cryptography 50.0.0 while those packages capped it below 50, so pip could not install it and pip install prowler silently fell back to 5.37.1 (#​12477)
• Pin zstd to 1.5.7.2; 1.5.7.3 was yanked from PyPI as not thread safe (#​12477)
• ECS task-definition checks no longer report PASS when DescribeTaskDefinition fails before container evidence is gathered (#​12478)
• ses_identity_not_publicly_accessible now evaluates every SES identity authorization policy and marks mixed public Allow and Deny statements for manual review (#​12480)

🔐 Security

• Trivy from v0.72.0 to v0.73.0 in the container image, fixing HIGH CVE-2026-46600 in the bundled golang.org/x/net (#​12445)
• Trivy v0.74.0 and Debian util-linux 2.41.5-0+deb13u1 in the SDK container image, patching Go standard library vulnerabilities and CVE-2026-53615 (#​12470)

v5.39.0: Prowler 5.39.0

Compare Source

✨ New features to highlight in this version

Enjoy them all now for free at https://cloud.prowler.com/

🤖 Lighthouse AI — Finding Skills

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

Lighthouse AI now embeds a Skills menu on every finding, answering the questions an analyst actually asks. Contextual Fix produces the fix for the finding, Triage Decision judges whether it is real and closes it out when it is not, and Systemic Scope determines whether the problem is a one-off or everywhere. A free-form "Ask Lighthouse anything" prompt sits in the same menu, and each run shows its progress and offers follow-up actions such as creating a Jira issue or muting the finding.

Read more in the Lighthouse AI documentation.

☁️ Azure Management Group Onboarding

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

Azure subscriptions no longer onboard one at a time. Choose "Add Multiple Subscriptions With Azure Management Group" in the add-provider wizard, enter the Microsoft Entra tenant ID, and authenticate once with a single tenant-wide service principal: Prowler discovers the entire management-group hierarchy under the tenant root, lets you select the subscriptions to onboard, and creates their providers with the management-group structure preserved. Azure now matches the one-step onboarding that AWS Organizations and GCP organizations already have.

Read more in the Azure Management Groups documentation.

✅ Findings Triage — Verify MANUAL Findings as PASS

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

Checks that require human judgment report MANUAL findings. For these findings, and only for them, the triage status selector now offers Resolved: choosing it asks for the required written evidence and verifies the finding as passing. The finding then reports an effective PASS while preserving the raw MANUAL scan result, across findings, finding groups, compliance reports, and scans, with the attestation's author, evidence, and validity always visible. Attestations expire automatically after 90 days, or as soon as a new scan reports a real failure, returning the finding to the review queue.

Read more in the Findings Triage documentation.

☁️ Prowler Cloud MCP — Organizations Management and Grouped Jira Dispatch

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

The hosted Prowler Cloud MCP server adds eight organization tools, so an agent can onboard and manage entire cloud organizations end to end: create the organization, discover its accounts, subscriptions, and projects, apply the selection, and manage the resulting providers. The tools cover AWS Organizations, GCP organizations, and Azure tenant root management groups, and they are available to Lighthouse AI.

prowler_send_findings_to_jira also gains Cloud-only dispatch capabilities: select failed findings by check IDs against the latest completed scan, and send them in grouped mode, one Jira work item per check listing up to 50 affected resources, with per-group error reporting.

Read more in the Prowler MCP tools documentation and its Jira operations reference.

🕸️ Attack Paths — Grouped Graph with Outcome Destinations

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

The Attack Paths graph now reads from source to destination. Resources of the same class collapse into a single expandable node with a count, clicking reveals its members, and every path terminates in an explicit outcome node naming the destination impact: code execution, privilege escalation, public exposure, or resource inventory. The per-account hub node is gone, and the clicked resource stays highlighted while its findings are expanded.

Explore the full Attack Paths query catalog at Prowler Hub.

Read more in the Attack Paths documentation.

📚 New Compliance Framework — CMMC 2.0

The Cybersecurity Maturity Model Certification (CMMC) is the certification the US Department of Defense requires from contractors and suppliers that handle federal contract data. Prowler now includes CMMC 2.0 as a universal framework with all 149 requirements defined by the CMMC Program rule (32 CFR Part 170), organized in its three levels:

• Level 1 (Foundational): 15 requirements for the basic safeguarding of Federal Contract Information, from FAR 52.204-21.
• Level 2 (Advanced): 110 requirements from NIST SP 800-171 Rev 2, protecting Controlled Unclassified Information.
• Level 3 (Expert): 24 enhanced requirements from NIST SP 800-172 for the most sensitive programs.

Requirements map to Prowler checks across AWS, Azure, GCP, Alibaba Cloud, Oracle Cloud, and Microsoft 365, so one framework reports the compliance posture of the whole estate.

Read more in the Compliance documentation.

🔍 Checks

Microsoft 365

Twenty new Entra ID checks expand the coverage of CIS Microsoft 365 Foundations Benchmark v7.0.0:

• Password protection: custom banned password list, on-premises enforcement, and lockout threshold and duration.
• Default user permissions: security group and Microsoft 365 group creation restricted, and guest invitations limited to allowed domains.
• Conditional Access: high and medium sign-in risk blocked, authentication transfer blocked, untrusted locations blocked, trusted named locations defined, sign-in frequency enforced, and token protection enforced.
• Sessions and authentication methods: idle session timeout configured, email one-time passcodes disabled, and Microsoft Authenticator context shown.
• PIM and access reviews: approval required to activate the Global Administrator and Privileged Role Administrator roles, and access reviews configured for guest users and privileged roles.

Explore all Microsoft 365 checks at Prowler Hub.

AWS

Two new checks detect hardcoded secrets:

• batch_job_definition_no_secrets scans Batch job definition environment variables and command parameters. Thanks to @​praneetrajv!
• awslambda_layer_no_secrets_in_content scans Lambda layer package content. Thanks to @​ganiganesh25!

Explore all AWS checks at Prowler Hub.

🙌 External Contributors

Thank you to our community contributors for this release!

• @​praneetrajv: AWS batch_job_definition_no_secrets check (#​12117)
• @​ganiganesh25: AWS awslambda_layer_no_secrets_in_content check (#​12233)
• @​andoniaf: GitHub organization_repository_creation_limited now reports low severity when repository creation is limited to private or internal visibility (#​12164)

---

UI

🚀 Added

• Manual verification workflow for MANUAL findings with evidence, effective PASS status, and expiration details (#​12253)
• Surface pre-configured credential creation links in the add-provider wizard. Cloudflare exposes the User API Token template and an Account-Owned template pinned to the Cloudflare Account ID entered in the wizard, GitHub exposes the personal-repositories template and an organization-scanning template pinned to the identifier entered in the wizard (#​12349)
• Attack Paths graph groups resources by class into expandable nodes and marks the query outcome as the terminal node, with the clicked resource highlighted while its findings are expanded (Prowler Cloud only) (#​12381)
• Azure Management Group onboarding: add every subscription in a tenant at once (Prowler Cloud only) (#​12386)
• Manage Lighthouse AI role permission in the role forms and role details, so permission to change the Lighthouse AI configuration can be granted or restricted independently of other permissions (Prowler Cloud only) (#​12412)
• CMMC 2.0 universal compliance framework rendering: dedicated icon, Domain/Level requirement mapper and cross-provider catalog tile (#​12414)

🐞 Fixed

• Organization discovery describes a too-deep hierarchy in each provider's own vocabulary: AWS organizational units, Azure Management Groups, Google Cloud folders (#​12386)
• View Findings on the Scans page no longer opens an empty list for users outside the UTC timezone (#​12411)

API

🔄 Changed

• GET /api/v1/users/me membership relationships identify the active tenant with meta.active for JWT and API key authentication (#​12388)

🐞 Fixed

• Tenant deletion no longer leaves memberships partially removed when exclusive-user cleanup fails (#​12379)
• /api/v1/accounts/saml/{organization_slug}/acs/ rejects non-POST requests before SAML response processing (#​12393)
• Social login derives a valid user name when identity providers omit the profile name (#​12413)

SDK

🚀 Added

• batch_job_definition_no_secrets check for AWS provider, scanning Batch job definition environment variables and command parameters for hardcoded secrets (#​12117)
• 7 M365 Entra checks covering CIS Microsoft 365 Foundations Benchmark v7.0.0 password protection, default user permissions, and guest invitation domain restrictions (#​12153)
• 7 M365 entra checks covering CIS Microsoft 365 Foundations Benchmark v7.0.0 Conditional Access (5.2.2.x) and idle session timeout controls (#​12154)
• entra_authentication_method_email_otp_disabled, entra_authentication_method_authenticator_show_context, entra_pim_global_administrator_approval_required, entra_pim_privileged_role_administrator_approval_required, entra_access_review_guest_users_configured and entra_access_review_privileged_roles_configured checks for M365 provider covering CIS Microsoft 365 Foundations Benchmark v7.0.0 authentication method, PIM approval and access review controls (#​12155)
• awslambda_layer_no_secrets_in_content check for AWS provider, scanning Lambda layer package content for hardcoded secrets (#​12233)
• CMMC 2.0 universal compliance framework (cmmc_2.0) with the 149 official requirements from 32 CFR Part 170 — Level 1 (15, 48 CFR 52.204-21), Level 2 (110, NIST SP 800-171 Rev 2) and Level 3 (24, NIST SP 800-172) — with AWS, Azure, GCP, Alibaba Cloud, Oracle Cloud and M365 check mappings and config guardrails (#​12401)

🔄 Changed

• GitHub organization_repository_creation_limited check now reports low severity for FAIL findings when repository creation is provably limited to private/internal visibility, instead of always reporting high (#​12164)

🔐 Security

• HTML report header now HTML-escapes every provider identity field across all 23 providers, closing a stored XSS in the header block (Secur0, CWE-79) that was left unaddressed by the earlier finding-row fix in #​12221 (#​12424)

v5.38.0: Prowler 5.38.0

Compare Source

✨ New features to highlight in this version

Enjoy them all now for free at https://cloud.prowler.com/

📌 Compliance Watchlist

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

Compliance Watchlist keeps the frameworks an organization tracks in one shared list. Pin frameworks from any compliance view, manage several at once through a searchable catalog, and filter the Compliance section to show only the pinned frameworks.

The Overview page now reports the latest score for every pinned framework, while finding details highlight the watched frameworks associated with each check. Universal frameworks remain a single watchlist entry across provider views, keeping the organization's priorities consistent everywhere.

Read more in the Compliance Watchlist documentation.

🔐 SAML SSO - Multiple Email Domains

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

One SAML configuration can now authorize a primary email domain and up to 19 additional domains through the same Identity Provider. Every domain shares one stable Assertion Consumer Service (ACS) URL based on the primary domain, so subsidiaries, acquired companies, regional domains, and multiple brands no longer require separate tenants or duplicated SAML applications.

Domain ownership remains tenant-bound throughout the authentication flow. During service provider-initiated sign-in, the discovery domain and the domain asserted by the Identity Provider must resolve to the same tenant before provisioning continues.

Read more in the SAML SSO documentation.

👥 User Sign-In Methods

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

The Users table now shows each account's sign-in methods as tags, including email/password, Google, GitHub, SAML with linked domains, and Partner SSO. Accounts without a reported method display a placeholder.

🕸️ Attack Paths - Expanded AWS Privilege-Escalation Coverage

Attack Paths adds 20 AWS privilege-escalation queries from pathfinding.cloud, while iam_policy_allows_privilege_escalation gains 22 additional escalation combinations.

The new coverage includes service iam:PassRole paths across AWS Batch, Braket, Cognito Identity, ECS, EMR, EMR Serverless, GameLift, Glue, EC2 Image Builder, Kinesis Analytics, HealthOmics, EventBridge Scheduler, Systems Manager, and Step Functions. It also covers existing-resource abuse, permissions-boundary removal, role assumption, and IAM Identity Center permission-set policy injection.

The query catalog now exposes each AWS query's outcome category, distinguishing code execution, privilege escalation, public exposure, and resource inventory.

Explore the full Attack Paths query catalog at Prowler Hub.

Read more in the Attack Paths documentation.

🔍 Checks

Microsoft 365

Twelve new checks expand the coverage of CIS Microsoft 365 Foundations Benchmark v7.0.0:

• Admin Center: Shared Bookings is disabled.
• Defender: Priority account protection and strict preset security policies are enabled.
• Entra ID: Six checks cover device registration restrictions, local administrator behavior, device limits, LAPS, and BitLocker key visibility.
• Exchange Online: Personal accounts in Outlook on the web are disabled and Direct Send is rejected.
• Microsoft Teams: External access from trial-only tenants is blocked.

Explore all Microsoft 365 checks at Prowler Hub.

🔐 Security

• Prowler API, UI, SDK, and MCP container images now publish per-architecture Software Bills of Materials (SBOMs) and build-provenance attestations. Prowler Cloud production and Prowler Private Cloud images carry the same attestations.
• SDK and API container builds verify the checksums of downloaded PowerShell, Trivy, and zizmor binaries before installation.
• Grype now complements Trivy across the container-image security gates, detecting components and vulnerabilities that manifest-based scanners can miss and blocking fixable high and critical findings.
• aiohttp was upgraded to 3.14.3 to address CVE-2026-69244. cryptography was upgraded to 50.0.0 to address CVE-2026-69247 and CVE-2026-69249.

---

UI

🚀 Added

• Sign-in method indicators in the Prowler Cloud Users table, including linked SAML domains (#​12268)
• Compliance watchlist: pin frameworks from any compliance view and filter every view down to the pinned ones, including the overview card and a finding's compliance chips (Prowler Cloud only) (#​12300)
• Multiple verified email domains in a single SAML configuration for Prowler Cloud (#​12332)
• Container images now ship an SBOM and build provenance as OCI attestations (#​12352)

🔄 Changed

• Add Provider wizard documentation link targeting each provider's credentials section and selected authentication method (#​12218)

🐞 Fixed

• Imported scans now appear on the Scans page even when no provider is connected (#​12025)
• Feedback widget no longer obscures page and side-panel actions (#​12282)
• Rows-per-page selector no longer disappears when the chosen page size collapses a table to a single page (#​12299)
• Overview ThreatScore card no longer leaves unused horizontal space at responsive layout boundaries (#​12317)
• Overview metric cards stack below the desktop layout threshold and preserve readable widths when aligned (#​12323)
• Overview metric cards now align horizontally at medium desktop widths (#​12323)
• AWS and GCP organization onboarding launches all linked provider scans through one bulk operation (#​12350)
• /compliance no longer fails while compliance overview data is still being generated (#​12358)
• Client Secret and Refresh Token labels in the GCP organization authentication form (#​12362)

🔐 Security

• Removed the apk upgrade from the UI image and moved the base digest forward instead, so the image is reproducible from its pin rather than from whatever Alpine serves at build time (#​12313)

API

🚀 Added

• Attack Paths adds 20 AWS privilege-escalation detection queries from pathfinding.cloud, covering service PassRole escalations (Batch, Braket, Cognito Identity, ECS, EMR, EMR Serverless, GameLift, Glue, EC2 Image Builder, Kinesis Analytics, HealthOmics, EventBridge Scheduler, SSM, Step Functions), CodeDeploy and Step Functions existing-resource abuse, role permissions-boundary removal with role assumption, and IAM Identity Center permission-set policy injection (#​12237)
• Attack Paths query metadata now carries an outcome (Code execution, Privilege escalation, Public exposure, or Resource inventory), exposed on the queries endpoint so the graph can show a terminal outcome node (#​12344)
• Container images now ship an SBOM and build provenance as OCI attestations (#​12352)

🔄 Changed

• Pin the container vulnerability scanner to Trivy v0.72.0, matching prowler-registry and partner-portal (#​12346)

🐞 Fixed

• Compliance report output directory failures are now logged with the exception attached and fingerprinted by errno in Sentry, so ENOSPC, ENOENT and EACCES no longer share a single issue (#​12142)
• Restored the SDK dependency to @master now that the dependency bumps have landed there, and regenerated the lock. The API image no longer builds against a temporary integration branch (#​12309)

🔐 Security

• The API container image now verifies the checksum of every third-party binary it downloads (PowerShell, Trivy, zizmor) before installing it (#​12334)
• Upgrade aiohttp to 3.14.3 to pick up the fix for CVE-2026-69244 (#​12340)
• Upgrade cryptography to 50.0.0, closing CVE-2026-69247 and CVE-2026-69249 (#​12356)

SDK

🚀 Added

• admincenter_shared_bookings_disabled check for M365 provider, covering CIS Microsoft 365 Foundations Benchmark v7.0.0 control 1.3.9 (#​12147)
• defender_priority_account_protection_enabled and defender_strict_preset_security_policy_enabled checks for M365 provider, covering CIS Microsoft 365 Foundations Benchmark v7.0.0 controls 2.4.1 and 2.4.2 (#​12148)
• exchange_owa_mailbox_policy_personal_accounts_disabled and exchange_organization_reject_direct_send_enabled checks for M365 provider, covering CIS Microsoft 365 Foundations Benchmark v7.0.0 controls 6.3.2 and 6.5.5 (#​12149)
• teams_external_access_trial_tenants_blocked check for M365 provider, verifying that Teams external access with trial-only tenants is blocked, covering CIS Microsoft 365 Foundations Benchmark v7.0.0 control 8.2.4 (#​12151)
• entra_device_registration_join_restricted, entra_device_registration_max_devices_per_user_limited, entra_device_registration_global_admins_not_local_admins, entra_device_registration_registering_user_not_local_admin, entra_device_registration_laps_enabled and entra_policy_default_user_cannot_read_bitlocker_keys checks for M365 provider, covering CIS Microsoft 365 Foundations Benchmark v7.0.0 device registration controls (5.1.4.x) (#​12152)
• The IAM privilege-escalation check now detects 22 additional pathfinding.cloud escalation paths across AWS Batch, Braket, CodeDeploy, Cognito Identity, ECS, EMR, EMR Serverless, GameLift, Glue, EC2 Image Builder, Kinesis Analytics, HealthOmics, EventBridge Scheduler, SSM Automation, Step Functions, IAM permissions boundaries, and IAM Identity Center (SSO) (#​12237)
• Container images now ship an SBOM and build provenance as OCI attestations (#​12352)

🔄 Changed

• Highlighted key security terms in the Risk description of 8 existing M365 checks (#​12156)
• Moved the Trivy suppressions from the classic .trivyignore to .trivyignore.yaml, so each entry is scoped to the package it names instead of suppressing its CVE across the whole image (#​12314)
• The securityhub_delegated_admin_enabled_all_regions, guardduty_delegated_admin_enabled_all_regions and config_delegated_admin_and_org_aggregator_all_regions checks now report MANUAL instead of FAIL when the delegated administrator status cannot be read and no independent misconfiguration is detected, which happens on member accounts that are not registered as delegated administrators because the API is restricted to the organization management account and to delegated administrator accounts (#​12319)
• Pin the container vulnerability scanner to Trivy v0.72.0, matching prowler-registry and partner-portal (#​12346)
• Quote the unquoted shell expansions in the release and build workflows (#​12365)
• Fix the remaining shellcheck findings in workflows and enable the check (#​12367)

🐞 Fixed

• Spurious error log output from Get-ApplicationAccessPolicy on M365 tenants without application access policies (#​12149)
• Secret checks no longer report credential-free JDBC connection strings as embedded credentials (#​12288)
• A failed ListOrganizationAdminAccounts lookup in one region no longer marks the Security Hub delegated administrator status as undetermined in every other region (#​12319)
• securityhub_delegated_admin_enabled_all_regions no longer reports FAIL with delegated administrator status could not be determined on accounts that do have a Security Hub delegated administrator; ListOrganizationAdminAccounts responses are now parsed with the AccountId and Status fields the API actually returns (#​12319)
• guardduty_delegated_admin_enabled_all_regions no longer reports no delegated administrator configured when the lookup was denied or failed, which asserted absence where there was only lack of visibility (#​12319)
• OCI Identity service no longer drops the whole dynamic groups, groups, policies or users listing when the OCI API returns null optional fields such as matching_rule (#​12327)
• Alibaba Cloud STS credential validation retries transient connection failures and reports exhausted attempts as connection errors instead of invalid credentials (#​12353)

🔐 Security

• Bumped the Compose DozerDB image from 5.26.3.0 to 5.26.27.0, which moves it off Debian 11 and onto Debian 13 (#​12320)
• The SDK container image now verifies the checksum of every third-party binary it downloads (PowerShell, Trivy, zizmor) before installing it (#​12334)
• Upgrade aiohttp to 3.14.3 to pick up the fix for CVE-2026-69244 (#​12340)
• Upgrade cryptography to 50.0.0, closing CVE-2026-69247 and CVE-2026-69249 (#​12356)

MCP

🚀 Added

• Test foundation for the MCP server with shared fixtures, JSON:API builders, mocked HTTP transports and CI coverage reporting (#​12291)
• Test coverage for the integrations tools and models, pinning the connection-check choreography and the Jira dispatch retry safety (#​12343)
• Container images now ship an SBOM and build provenance as OCI attestations (#​12352)

🔄 Changed

• prowler_send_findings_to_jira now reports safe_to_retry on every outcome, true only when Prowler knows no Jira work item was created: a dispatch the API refused is retryable, one that failed on the server or got no answer is not (#​12343)
• prowler_list_integrations no longer requests the configuration it discards, now that the API tolerates a sparse fieldset without it (#​12343)

🔐 Security

• Upgrade cryptography to 50.0.0, closing CVE-2026-69247 and CVE-2026-69249 (#​12356)

v5.37.1: Prowler 5.37.1

Compare Source

UI

🐞 Fixed

• Fixed image optimization in the production container: Next.js standalone tracing omitted sharp's native libvips library, so every image was served unoptimized (#​12307)

🔐 Security

• The UI container image now patches musl and zlib alongside OpenSSL, and sharp is pinned to 0.35.3, clearing the image's remaining CVEs (#​12307)

API

🐞 Fixed

• Entra Conditional Access guest-user checks no longer report false FAILs in M365 scans: microsoft-kiota packages overridden to 1.9.10 so guestOrExternalUserTypes (a flags enum Graph serializes as a comma-separated string) deserializes correctly instead of returning an empty list (#​12315)

🔐 Security

• The API container image now builds on Debian 13 (trixie), taking its critical CVE count from 18 to 4 (#​12311)
• Bumped PowerShell, Trivy and uv in the API container image, clearing 14 high-severity CVEs (#​12311)
• Bumped workos and pyopenssl so the API can move to cryptography 48.0.1 (#​12311)
• Removed gnupg and apt-transport-https from the API container image (#​12311)
• The API container image no longer ships git; removing it also dropped perl, perl-modules, libperl and liberror-perl, clearing 12 critical CVEs. Only perl-base remains, which Debian marks Essential and cannot be removed (#​12311)
• Removed pip from the API container image, clearing two high-severity CVEs in the vendored copies of setuptools and msgpack (#​12311)
• Bumped pillow to 12.3.0, httplib2 to 0.32.0 and pyasn1 to 0.6.4 to resolve known CVEs (#​12311)

SDK

🔄 Changed

• Huawei Cloud exception codes moved from 19000-19007 to 20000-20007, resolving a collision with E2E Networks which reserves 19000-19999 (#​12306)

🐞 Fixed

• Checks registered through the prowler.checks.<provider> entry-point group can now run against built-in providers. The built-in probe in _resolve_check_module used a bare find_spec, which imports the parent package to search it and so raised ModuleNotFoundError for a plug-in check instead of returning None, aborting the lookup before the entry points were consulted. Such a check was discovered, listed and selected for execution, then silently produced no findings. (#​12312)
• Entra Conditional Access guest-user checks no longer report false FAILs: microsoft-kiota packages bumped to 1.9.10 so guestOrExternalUserTypes (a flags enum Graph serializes as a comma-separated string) deserializes correctly instead of returning an empty list (#​12315)

🔐 Security

• Bumped the Compose postgres and valkey images, clearing 10 critical CVEs (#​12307)
• Bumped PowerShell, Trivy, uv and joserfc in the container images, clearing 14 high-severity CVEs from the SDK and API images (#​12307)
• Bumped httplib2 to 0.32.0 and pyasn1 to 0.6.4 to resolve known CVEs (#​12307)
• The SDK container image now builds on Debian 13 (trixie), clearing the unfixable libsqlite3-0 and zlib1g criticals (#​12307)
• Bumped cryptography to 48.0.1 to resolve GHSA-537c-gmf6-5ccf, along with the oci, alibabacloud-tea-openapi, darabonba-core and py-ocsf-models bumps it requires (#​12307)
• Removed pip from the SDK container image, clearing two high-severity CVEs in the vendored copies of setuptools and msgpack (#​12307)
• Removed wget, gnupg and apt-transport-https from the SDK runtime image (#​12307)

MCP

🔐 Security

• Bumped fastmcp and pinned cryptography, joserfc, mcp and python-multipart, clearing all 7 high-severity CVEs from the MCP image (#​12307)

v5.37.0: Prowler 5.37.0

Compare Source

✨ New features to highlight in this version

Enjoy them all now for free at https://cloud.prowler.com

💬 Lighthouse AI — Context-Aware Chat and a Bigger Toolbox

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

Lighthouse AI is now aware of your working context when in Prowler Cloud. Messages carry page-aware context — the page you are on, the finding or resource open in the side panel, and its metadata — so "explain this" just works, and each page offers concise contextual suggestions to start from.

Lighthouse also gained access to every tool family the Prowler MCP server advertises: scan configurations, scan scheduling, finding triage, alert rules and recipients, integrations, users, and roles. Every action remains gated by RBAC: Lighthouse AI can only do what the user asking could do themselves.

Read more in the Lighthouse AI documentation.

🔌 Prowler MCP — Integrations, Users, and Roles

Prowler MCP gained three tool families, available on both the Cloud and the self-hosted Local MCP Server:

• Integrations — manage where Prowler sends its results, with the full lifecycle for Amazon S3, AWS Security Hub, and Jira: create them, update credentials, configuration and attached providers, re-check connections, and delete them — plus turning findings into Jira work items directly from a conversation.
• Users — read-only tools to list the tenant users with their emails and identify the authenticated user.
• Roles — browse the RBAC roles defined in the tenant, inspect the capabilities each one grants, and set the role a user holds.

Read more in the Prowler MCP tools reference.

☁️ Prowler MCP — Cloud-Only Tools

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription. These tools are exposed only by the Cloud MCP Server at https://mcp.prowler.com/mcp; the self-hosted Local MCP Server does not include them.

A new prowler_cloud_* namespace adds 32 tools so your AI assistant can run Prowler Cloud workflows end to end instead of only reading from them:

• Alerts — create and manage alert rules and email recipients, and browse the fired-alert history. Rule conditions can be dry-run before saving, so you can see what a rule would match without persisting anything.
• Findings Triage — set a finding's triage status and attach notes documenting the decision. Unlike muting, the finding stays visible.
• Scan Scheduling — configure daily, interval, weekly, or monthly recurring scans, one provider at a time or applied across many at once.
• Scan Configurations — build reusable scan configuration and attach them to providers.

Read more in the Prowler Cloud MCP tools reference.

🧭 Compliance — Grouped by provider of the same type

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

One framework, every provider, a single answer. Building on the cross-provider-type roll-up, the Compliance section now groups compliance for all providers of the same type: a single-provider framework — CIS AWS, CIS GCP, ENS for Azure — is aggregated across the latest completed scan of every provider of that type. Each framework card rolls up into a consolidated posture with a per-provider breakdown, a findings drill-down, and a combined executive PDF report. Requirement status follows the same strict precedence (FAIL over PASS over MANUAL), so one failing provider flags the requirement for the whole estate.

The Compliance tabs were also renamed to say what they aggregate: "Per Scan" is now Single Scan, "Cross-Provider" is now Multiple Scans, and Compliance lands on Multiple Scans by default.

Read more in the Cross-Provider Compliance documentation.

☁️ GCP Organization Onboarding

[!NOTE]
This feature is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

Onboarding an entire Google Cloud organization is now a single guided flow. Provide an organization-level credential and Prowler discovers the full hierarchy, every folder and project. Pick the folders and projects to onboard from a selection tree, set custom aliases, test the connection, and launch: each selected project is registered as a provider, with no need to add them one by one. Post-onboarding management is covered too, including credential replacement and organization-wide deletion.

Read more in the GCP Organizations documentation.

🕸️ Attack Paths — More Privilege Escalation Queries

Attack Paths adds four AWS privilege-escalation detection queries from pathfinding.cloud. Thanks to @​paramanandmallik!

• STS-002 — cross-account role trust
• STS-003 — wildcard role trust
• IAM-022 — user permissions-boundary removal
• SSO-001 — IAM Identity Center permission-set escalation

The query info panel now links every query to its page on Prowler Hub, and the IAM privilege-escalation queries were reworked to run efficiently on accounts with many IAM roles, users, or groups, fixing runtime errors and timeouts on large graphs.

Read more in the Attack Paths documentation.

🛡️ AWS Confidential Computing — Nitro Enclaves Checks

Prowler adds the first CSPM coverage for confidential computing workloads on AWS, with 11 new checks for Nitro Enclaves, developed together with Guillermo Ruiz from AWS.

• Workload host environment (EC2) — five ec2_confidential_workload_host_* checks for the parent instance: IMDSv2 not enforced, public IP exposure, unrestricted ingress, exposed vsock proxy ports, and hosts not running.
• KMS attestation policy — six kms_key_enclave_* checks for the key policies gating enclave secrets: attestation not enforced or bypassable, missing deployment binding, debug-mode attestations, PCR mismatches, and unknown enclave images.

All checks are fully passive, using AWS APIs and CloudTrail with no instance access or SSM agent required, and are mapped across 23 compliance frameworks, including NIST 800-53 Rev 5, PCI-DSS v4.0, ISO 27001:2022, SOC 2, HIPAA, and MITRE ATT&CK.

Read more about it this blog post.

Try them out now at cloud.prowler.com!

🏢 New Provider — Huawei Cloud

Prowler now scans Huawei Cloud, with 25 checks across ten services: CTS, ECS, ELB, EVS, IAM, KMS, OBS, RDS, VPC, and WAF, plus the CIS Huawei Cloud Foundations Benchmark 1.0 compliance framework. Thanks to @​tomitobio for their 1st provider in Prowler!

To scan a Huawei Cloud account, export the IAM user's access key credentials and run Prowler CLI:

export HUAWEICLOUD_ACCESS_KEY_ID="your-access-key-id"
export HUAWEICLOUD_SECRET_ACCESS_KEY="your-secret-access-key"

prowler huaweicloud

Read more in the Huawei Cloud documentation. Explore all Huawei Cloud checks at Prowler Hub.

🔍 Checks

AWS

• codecommit_repository_no_secrets, alongside the new codecommit service, scans files tracked at the tip of each repository's default branch for hardcoded secrets. Thanks to @​Sid-0602!
• glue_catalog_connection_no_secrets detects secrets in Glue Data Catalog connection properties. Thanks to @​l46983284-cpu, @​Rishi943, and @​UTKARSH698!
• ec2_instance_stopped_older_than_specific_days detects EC2 instances stopped longer than a configurable number of days (default 30). Thanks to @​Nithin078!
• sagemaker_endpoint_config_kms_encryption_enabled verifies SageMaker endpoint configurations use a KMS key for storage volume encryption. Thanks to @​Nithin078 and @​l46983284-cpu!

Read more in the AWS documentation.

Explore all AWS checks at Prowler Hub.

📤 OCSF Output — MITRE ATT&CK Enrichment

OCSF detection finding output now populates finding_info.analytic with the Prowler check rule and finding_info.attacks with MITRE ATT&CK technique and tactic objects for findings with MITRE ATT&CK compliance metadata. Thanks to @​AlexanderSanin!

🐞 Fixed

• AWS Security Hub integrations now persist successful recovery checks during finding delivery, keeping connection status and the last-checked time accurate.
• Social sign-up now creates authentication, tenant, and membership records in a single transaction, fully rolling back failed provisioning to prevent incomplete accounts.
• The SAML configuration form keeps the ACS URL field stable while generating the callback URL and exposes the copy action only after a valid URL is available.
• SAML users without a userType attribute and without an existing role now receive a least-privilege read_only fallback role, so role-dependent operations continue to work without granting management permissions.

🔐 Security

• Provider deletion, connection checks, scan creation, provider secrets, provider groups, and daily schedules now respect role provider-group visibility.
• HTML reports escape provider-originated finding fields, preventing stored cross-site scripting through malicious cloud resource tags. GHSA-c2jg-2778-ggm4
• Authentication with an API key whose owning user was deleted now returns 401, and user deletion revokes the user's API keys across all their tenants.

🙌 External Contributors

Thank you to our community contributors for this release!

• @​tomitobio: Huawei Cloud provider with CIS 1.0 benchmark (#​11950)
• @​paramanandmallik: four AWS privilege-escalation Attack Paths queries (#​11460)
• @​Sid-0602: AWS codecommit service and codecommit_repository_no_secrets check (#​11846)
• @​l46983284-cpu, @​Rishi943, and @​UTKARSH698: AWS glue_catalog_connection_no_secrets check (#​11963)
• @​Nithin078: AWS ec2_instance_stopped_older_than_specific_days (#​12076) and sagemaker_endpoint_config_kms_encryption_enabled (#​12118, co-authored with @​l46983284-cpu) checks
• @​AlexanderSanin: MITRE ATT&CK enrichment in OCSF detection finding output (#​11492)
• @​stefanobaldo: GCP gen2 Cloud Functions IAM policy retrieval is now thread-safe (#​12107)
• @​rayair250-droid: GCP SSH and RDP firewall checks now detect exposed ports in any position within multi-port rules (#​12115)
• @​jbchief-dev: secret ignore patterns now use Kingfisher-compatible LF line indexing (#​12141)
• @​bmbferreira: Helm chart improvements — immutable chart versions on release (#​12056) and capped Celery worker concurrency (#​12054)

---

UI

🚀 Added

• Lighthouse AI contextual messages with page-aware prompts, focused side-panel details, selected-resource metadata, and retry-safe historical badges (#​12069)
• Cross-account compliance view in the Multiple Scans tab: an "Across providers" section listing single-provider frameworks aggregatable across every account of the same provider type, with a per-account detail, findings drill-down and combined PDF report (Prowler Cloud only) [(#&chore(deps): update aws-cdk monorepo to v2.66.0 #8

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks