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

[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.38.0

---

Release Notes

prowler-cloud/prowler (toniblyx/prowler)

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) (#​12086)
• In Prowler Cloud, authenticated users can send product feedback through a persistent widget backed by a PostHog headless survey, rendered with native Prowler components and editable from the PostHog dashboard (#​12116)
• Attack Paths query info panel now links every query to its page on Prowler Hub (#​12145)
• Warning before replacing an organization credential or deleting an organization, listing the providers affected (#​12255)
• GCP organization onboarding in the provider wizard: add every project of an organization at once, choosing which discovered projects to include (Prowler Cloud only) (#​12255)
• Sign-up campaign attribution preserves promo_code and utm_* params across auth redirects, sign-in/sign-up links, Google/GitHub OAuth callbacks, and POST /users (#​12269)

🔄 Changed

• /compliance now lands on the Multiple Scans tab; links carrying a scanId keep opening Single Scan (#​12086)
• Compliance tab naming: "Per Scan" is now "Single Scan" and "Cross-Provider" is now "Multiple Scans", with matching "Across provider types" and "Across providers" section headers explaining each aggregation axis (#​12086)
• Lighthouse contextual suggestions now show concise actions while preserving detailed prompts for chat (#​12219)
• Providers page groups GCP projects under their organization and folders (#​12255)

🐞 Fixed

• Attack Paths now classify cloud-provider finding resources separately from Prowler findings (#​11244)
• Finding delta colors and integration update button labels restored (#​12160)
• Long unbroken messages in Lighthouse chat no longer overflow their message bubble (#​12215)
• SAML ACS URL field remains visible while generating the callback URL from the email domain (#​12236)

API

🚀 Added

• Attack Paths: four AWS privilege-escalation detection queries from pathfinding.cloud: cross-account role trust (STS-002), wildcard role trust (STS-003), user permissions-boundary removal (IAM-022), and IAM Identity Center permission-set escalation (SSO-001) (#​11460)

🐞 Fixed

• Attack Paths IAM privilege-escalation queries no longer build an all-nodes × all-resource-items cartesian product, fixing runtime errors and timeouts on accounts with many IAM roles, users, or groups (#​12136)
• task_args serialization no longer returns HTTP 500 errors when Celery truncates stored task keyword arguments (#​12165)
• Attack Paths predefined queries on migrated graphs are now scoped with the provider label, letting the graph database seed from its label index instead of a global label scan and preventing query timeouts on Neptune (#​12167)
• Authentication with an API key whose owning user was deleted now returns 401 instead of an unhandled AttributeError, and user deletion now revokes the user's API keys across all their tenants (#​12210)
• AWS Security Hub integrations now persist successful connection checks during finding delivery so their connection status and last checked timestamp stay current (#​12212)
• SAML users without a userType attribute and without an existing role in the SAML tenant now receive a least-privilege read_only fallback role; a numeric suffix is used when that name belongs to a role with different permissions (#​12223)
• Social signups create users and authentication records in one database transaction, preventing incomplete accounts when provisioning fails (#​12245)
• Requesting integrations with a sparse fieldset that leaves out configuration no longer returns HTTP 500 errors when the tenant has a Jira integration (#​12261)

🔐 Security

• Provider deletion and connection checks, scan creation, provider secrets, provider groups, and daily schedules now respect role provider-group visibility (#​12216)

SDK

🚀 Added

• OCSF detection finding output now populates finding_info.analytic as the Prowler check rule and finding_info.attacks as MITRE ATT&CK technique and tactic objects for findings with MITRE-ATTACK compliance metadata (#​11492)
• codecommit service and codecommit_repository_no_secrets check for AWS provider, scanning files tracked at the tip of each repository's default branch for hardcoded secrets (#​11846)
• Huawei Cloud provider, with CTS, ECS, ELB, EVS, IAM, KMS, OBS, RDS, VPC and WAF services and a CIS 1.0 compliance benchmark (#​11950)
• glue_catalog_connection_no_secrets check to detect secrets in Glue Data Catalog connection properties (#​11963)
• ec2_instance_stopped_older_than_specific_days check for AWS provider, detecting EC2 instances stopped longer than a configurable number of days (default 30) (#​12076)
• sagemaker_endpoint_config_kms_encryption_enabled check verifying SageMaker endpoint configurations use a KMS key for storage volume encryption (#​12118)
• 11 AWS Nitro Enclaves security checks providing the first CSPM coverage for confidential computing workloads, covering both host environment (ec2_confidential_workload_host_*) and KMS attestation policy (kms_key_enclave_*), fully passive via boto3 and CloudTrail LookupEvents (#​12283)

🐞 Fixed

• Scan configuration schema no longer exposes SDK/CLI-only providers such as e2enetworks; the aggregated schema served by /scan-configurations/schema now includes only app providers (sdk_only = False) (#​12094)
• GCP Cloud Functions gen2 IAM policy retrieval now uses a per-request HTTP client, preventing a process crash from concurrent thread-unsafe httplib2 access when a project has several gen2 functions (#​12107)
• GCP firewall SSH and RDP checks now detect exposed target ports in any position within multi-port rules (#​12115)
• Secret ignore patterns now use Kingfisher-compatible LF line indexing for scanned content containing ASCII control characters (#​12141)
• Jira descriptions with inline code nested in bold or italic Markdown now render as valid ADF (#​12158)

🔐 Security

• HTML reports escape provider-originated finding fields to prevent stored cross-site scripting through malicious cloud resource tags (#​12221)

MCP

🚀 Added

• Read-only user management tools prowler_list_users, prowler_get_user, and prowler_get_current_user for listing tenant users with their emails and identifying the authenticated user (#​12088)
• RBAC role tools prowler_list_roles, prowler_get_role, prowler_get_user_roles, and prowler_set_user_role for browsing roles and setting the role a user holds (#​12088)
• Integrations tools to manage Amazon S3, AWS Security Hub and Jira integrations, and to send findings to Jira (#​12138)

🔄 Changed

• README now documents the Cloud-only prowler_cloud_* tools available on the hosted Prowler MCP (alerts, findings triage, scan scheduling, scan configurations), and corrects the Prowler Hub check count and the scan orchestration capabilities (#​12266)

🐞 Fixed

• Memory leak in HTTP mode caused by streamable-HTTP sessions being retained for the process lifetime when clients never sent DELETE /mcp; the server now runs stateless (#​12235)
• prowler_list_integrations failing with a 500 error on tenants with a Jira integration, caused by the request leaving configuration out of the sparse fieldset (#​12259)

v5.36.0: Prowler 5.36.0

Compare Source

✨ New features to highlight in this version

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

🎫 Finding Groups - Jira

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

Selected Findings, Finding Groups, and mixed selections can now be sent to Jira. When you select multiple findings, choose between one grouped issue or separate issues. Generated issues keep their Prowler context with deep links and filter details, while the UI provides clear dispatch and failure feedback.

Read more in our Jira integration documentation.

🕸️ Attack Paths - Queries

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

Prowler Cloud now records which built-in Attack Paths queries returned data at the end of each scan. The query selector hides confirmed-empty queries for the selected scan, so you can focus on paths that exist without opening blank graph views. Errored, unknown, and parameterized queries remain available when they still require investigation or input.

All Attack Paths queries are now published on Prowler Hub, where you can browse the full catalog.

Read more in our Attack Paths documentation.

🧑‍🏫 New Tutorials: Connect Your AI Agents to Prowler Cloud

[!NOTE]
For this feature you need a Prowler Cloud API key so this is available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription.

New tutorials walk you through connecting your own AI agents to Prowler Cloud, so they can query your security posture and act on it programmatically.

Read more in our AI agents documentation.

☁️ Region-less Oracle Cloud Infrastructure Setup

Oracle Cloud Infrastructure (OCI) provider credentials no longer require a region. Existing clients can still send the legacy region field for compatibility, but the API ignores it before storing credentials or starting a scan. This removes an unnecessary step from OCI onboarding.

Read more in our OCI documentation.

🔍 Checks

AWS

• sagemaker_notebook_instance_no_secrets scans the OnCreate and OnStart lifecycle scripts of SageMaker notebook instances for hardcoded API keys, passwords, tokens, connection strings, and other secrets. Thanks to @​kiranrajsg!

Read more in our AWS documentation.

Explore all AWS checks at Prowler Hub.

🔐 Security

• Integration responses and operations now respect provider visibility, preventing hidden-provider disclosure and blocking unauthorized attachment, connection checks, Jira dispatches, edits, and deletion.
• Next.js was updated from 16.2.9 to 16.2.11, patching four high-severity and five medium-severity vulnerabilities.
• The unused npm CLI was removed from the UI container image, eliminating the bundled node-tar CVE-2026-59873 and reducing exposure to future bundled npm vulnerabilities.
• Vitest and its browser packages were updated from 4.1.8 to 4.1.10, resolving the critical @vitest/browser file-access permission bypass. These are development dependencies and have no runtime impact.
• Kubernetes kubeconfig validation now blocks legacy auth-provider.config.cmd-path command authentication, closing a command-execution bypass. GHSA-ccqh-6cjc-wp4j
• next-auth was updated from 5.0.0-beta.30 to 5.0.0-beta.32, patching two critical Auth.js advisories: existence-based authorization checks that could fail open when a provider is misconfigured, and a homoglyph @ bypass in email address normalization. The bump also pulls in the patched @auth/core 0.41.3 transitively.

🙌 External Contributors

Thank you to our community contributors for this release!

• @​kiranrajsg: AWS sagemaker_notebook_instance_no_secrets check (#​11843)
• @​owenchenxy: Alibaba Cloud SSH and RDP security group checks now handle capitalized Policy="Accept" values correctly (#​12049)
• @​rsaladra: S3 bucket name validation no longer raises an invalid escape sequence SyntaxWarning at startup (#​12041)
• @​SujayKulkarni-2211 - Updated the AWS check count in the README (#​12011)

---

UI

🚀 Added

• Finding Groups and grouped selections can be sent to Jira in Cloud with deep links, filter chip display, and Jira feedback toasts (#​12001)
• In Prowler Cloud, the Attack Paths query selector now lists only queries that returned data for the selected scan, hiding empty ones (#​12010)
• Overview banner linking to the AI agents documentation, shown next to the Lighthouse AI banner in Cloud and full width on self-hosted deployments (#​12074)

🐞 Fixed

• Findings Severity Over Time chart Y-axis labels no longer overflow for large findings counts (#​11545)
• UI Sentry alerts now suppress non-actionable warnings and expected API/control-flow noise while preserving actionable runtime failures (#​11665)
• OCI provider E2E tests no longer require or submit a region when adding or updating credentials (#​11741)
• Billing navigation is hidden when Cloud billing is disabled, including Enterprise deployments (#​12047)
• AWS Organizations setup modal now s

✂ 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