CVE-2026-73264: CWE-918: Server-Side Request Forgery (SSRF) in prowler-cloud prowler
Prowler is a cloud security platform. Prior to 5.33.1, an authenticated user with Lighthouse provider configuration access could supply an unvalidated base_url for the openai_compatible provider through POST /api/v1/lighthouse/providers and POST /api/v1/lighthouse/providers/{id}/connection, causing api/src/backend/tasks/jobs/lighthouse_providers.py to send outbound requests, including the API key in the Authorization header, to attacker-controlled or internal endpoints when client.models.list was called. This issue is fixed in version 5.33.1.
AI Analysis
Technical Summary
The vulnerability exists in prowler versions before 5.33.1 where an authenticated user with Lighthouse provider configuration access can supply an unvalidated base_url parameter for the openai_compatible provider via specific POST API endpoints. This leads to the backend task in lighthouse_providers.py making outbound HTTP requests to attacker-controlled or internal endpoints, including the API key in the Authorization header. This SSRF flaw could allow attackers to leverage the API key to access sensitive resources. The issue is resolved in version 5.33.1.
Potential Impact
An attacker with authenticated access and Lighthouse provider configuration permissions can cause the backend to send requests to arbitrary endpoints, potentially exposing the API key in the Authorization header to attacker-controlled or internal services. This could lead to unauthorized access to sensitive data or internal systems. The CVSS score of 7.6 (high) reflects the critical confidentiality impact and limited integrity impact, with no availability impact.
Mitigation Recommendations
Upgrade prowler to version 5.33.1 or later, where this SSRF vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed fixed in 5.33.1.
CVE-2026-73264: CWE-918: Server-Side Request Forgery (SSRF) in prowler-cloud prowler
Description
Prowler is a cloud security platform. Prior to 5.33.1, an authenticated user with Lighthouse provider configuration access could supply an unvalidated base_url for the openai_compatible provider through POST /api/v1/lighthouse/providers and POST /api/v1/lighthouse/providers/{id}/connection, causing api/src/backend/tasks/jobs/lighthouse_providers.py to send outbound requests, including the API key in the Authorization header, to attacker-controlled or internal endpoints when client.models.list was called. This issue is fixed in version 5.33.1.
CVSS v3.1
Score 7.6high
Affected software
pkg:github/prowler-cloud/prowlerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in prowler versions before 5.33.1 where an authenticated user with Lighthouse provider configuration access can supply an unvalidated base_url parameter for the openai_compatible provider via specific POST API endpoints. This leads to the backend task in lighthouse_providers.py making outbound HTTP requests to attacker-controlled or internal endpoints, including the API key in the Authorization header. This SSRF flaw could allow attackers to leverage the API key to access sensitive resources. The issue is resolved in version 5.33.1.
Potential Impact
An attacker with authenticated access and Lighthouse provider configuration permissions can cause the backend to send requests to arbitrary endpoints, potentially exposing the API key in the Authorization header to attacker-controlled or internal services. This could lead to unauthorized access to sensitive data or internal systems. The CVSS score of 7.6 (high) reflects the critical confidentiality impact and limited integrity impact, with no availability impact.
Mitigation Recommendations
Upgrade prowler to version 5.33.1 or later, where this SSRF vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed fixed in 5.33.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-11T17:18:01.599Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7c89c6bf8831d539b3d5e1
Added to database: 08/12/2026, 14:57:10 UTC
Last enriched: 08/12/2026, 15:11:14 UTC
Last updated: 08/12/2026, 16:12:46 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.