✨ New features to highlight in this version

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

🧭 Add Provider — One Step to Connect Any Provider

The add-provider wizard follows the same model for every provider: one connect step, then the launch step. The account, its alias and its credentials are one form, and a single submit registers the account, stores the secret and tests the connection.

• A failed connection test shows inline, keeps the values and turns the action into "Retry connection" without registering the account twice.
• Access methods show as cards on the same step for AWS, GCP, Microsoft 365, GitHub, Alibaba Cloud and Cloudflare, and AWS, Azure and GCP switch to their organization flow through tabs.
• Users with the Manage Account permission can invite a teammate to finish the connection for every provider, not only AWS.
• "Ask Lighthouse AI" opens beside the wizard without closing it. It guides the connection from the Prowler docs by default and, when asked, connects the provider itself after confirming the provider, UID and credential field names, never echoing a secret back.
• Product tours and the guided onboarding sequence are removed; new tenants still land on the add-provider wizard.

🎯 Prowler Cloud — Issues Verdicts Explained

• The Issues list leads with the verdict, shows the attack path under each title and adds a "Why" column with the five evidence legs, so the reason for a verdict reads without opening the issue.
• A row opens in the side panel, next to Lighthouse AI, with the verdict, legs, remediation, triage and an "Attack path" tab with the issue graph.
• The menu entry is renamed to "Exploitability issues".

☁️ Azure and AWS Checks

• network_application_gateway_waf_enabled and network_application_gateway_http2_enabled cover Azure Application Gateways and their WAF policies, mapped to CIS 5.0 and 6.0. Contributed by @BabafemiB. Thank you!
• iam_subscription_owners_between_2_and_3 verifies that each Azure subscription has between two and three Owners, counting owners inherited from management groups, mapped to CIS 5.0 and 6.0. Contributed by @BabafemiB. Thank you!
• The AWS security group internet exposure checks treat CIDRs in one ingress rule that together cover 0.0.0.0/0 or ::/0, such as 0.0.0.0/1 plus 128.0.0.0/1, as open to the internet; such a rule used to pass ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22 and its siblings. Contributed by @harshrajdebug. Thank you!

Explore all checks at Prowler Hub.

🛠️ Improvements and Fixes

• Every MCP Server tool declares readOnlyHint and destructiveHint, so clients can tell a listing from a write when deciding whether to ask the user. Mutelist and mute rule writes are marked destructive because they hide findings for good.
• The cross-provider compliance tab keeps the frameworks that loaded, with a warning, when one catalog page or framework fails, instead of going blank.
• The NATO D32 compliance framework has its own icon on the compliance cards.
• Lighthouse AI replies no longer blink when the response finishes streaming, and the user avatar no longer requests the current page as an image, which rendered every page twice.
• The Invitations page uses "Status" instead of "State", and the Invitations and Roles filters show capitalized options.
• Prowler Cloud: actions refused because the tenant is over its plan's usage limit, such as launching a scan, saving a schedule, adding a provider or triaging a finding, now link to the plans page.
• Prowler Cloud: creating API keys is a Prowler Cloud feature; on Local Server the button opens the upgrade dialog, and existing keys can still be edited and revoked.
• Prowler Private Cloud: Lighthouse AI can use Amazon Bedrock with only a region, relying on the installation's own AWS role, when the API allows it.

🔐 Security Updates

• pymongo upgraded to 4.18.3, dnspython to 2.9.0 and oauthlib to 4.0.0 in the SDK and the API container image, patching the BSON decoding and DNS compression pointer denial of service advisories and the OAuth device flow token disclosure. The API also moves django-allauth to 65.19.7, since earlier releases cap oauthlib below 4.
• Authlib upgraded to 1.9.1 and dnspython to 2.9.0 in the MCP Server container image, patching CVE-2026-96760 (critical), CVE-2026-114615, CVE-2026-114616 and CVE-2026-114605.

🙌 External Contributors

Thank you to our community contributors for this release!

• @BabafemiB: Azure network_application_gateway_waf_enabled, network_application_gateway_http2_enabled and iam_subscription_owners_between_2_and_3 checks (#13160, #13145)
• @harshrajdebug: AWS security group internet exposure fix for split CIDRs (#13191)

See the full release notes on GitHub for the complete list of changes.

UI

🚀 Added

• Icon for the NATO D32 compliance framework on the compliance cards (#13174)

🔄 Changed

• Invitations page uses Status instead of State in the filter, table column and invitation details, and the Invitations and Roles filters show capitalized options (#13175)
• Product tours and the guided onboarding sequence are no longer shown; new tenants still land on the add-provider wizard (#13176)
• Add provider wizard connects every provider in one step, saving the account and credentials and testing the connection together, with teammate invitations for every provider and Lighthouse AI help beside the steps (#13181)

🐞 Fixed

• User avatar requesting the current page as an image on every load, which rendered each page twice (#13177)
• Lighthouse AI reply blanking out for a frame when the response finishes streaming, which made the whole text blink and reappear (#13180)
• Compliance cross-provider tab no longer blanks out when a single catalog page or framework fails to load; it shows the frameworks that loaded with a warning instead (#13183)

API

🔐 Security

• pymongo to 4.18.3, dnspython to 2.9.0 and oauthlib to 4.0.0 in the API container image, with django-allauth from 65.15.0 to 65.19.7 because earlier releases cap oauthlib below 4, patching the BSON decoding and DNS compression pointer denial of service advisories and the OAuth device flow token disclosure (#13185)

SDK

🚀 Added

• iam_subscription_owners_between_2_and_3 check for Azure provider, verifying each subscription has between 2 and 3 principals with the Owner role, including owners inherited from management groups, mapped to CIS 5.0 and 6.0 (#13145)
• network_application_gateway_waf_enabled and network_application_gateway_http2_enabled checks for Azure provider, with Application Gateway and WAF policy collection in the network service, mapped to CIS 5.0 and 6.0 (#13160)

🐞 Fixed

• Security group internet exposure checks now treat CIDRs in one ingress rule that together cover 0.0.0.0/0 or ::/0 as open to the internet (#13191)

🔐 Security

• pymongo to 4.18.3, dnspython to 2.9.0 and oauthlib to 4.0.0 in the SDK, patching the BSON decoding and DNS compression pointer denial of service advisories and the OAuth device flow token disclosure; dnspython stays on 2.8.0 for Python 3.10, which 2.9.0 no longer supports (#13185)

MCP

🚀 Added

• readOnlyHint and destructiveHint annotations on every MCP tool, with mute rule and mutelist writes marked destructive (#13196)

🔐 Security

• Authlib from 1.7.2 to 1.9.1 and dnspython from 2.8.0 to 2.9.0 in the MCP Server container image, patching CVE-2026-96760 (critical), CVE-2026-114615, CVE-2026-114616 and CVE-2026-114605 (#13186)