SSRF (Server-Side Request Forgery) in Prowler (CVE-2026-73264)
Summary
SSRF in Prowler (CVE-2026-73264). Confidential information can be exposed externally. Exploitable via POST /api/v1/lighthouse/providers.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73264 has been found in Prowler.
Attackers can target a specific entry point like POST /api/v1/lighthouse/providers over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Prowler CVE-2026-73264" on the vendor's site.
CVE-2026-73264 (Prowler) — CWE-918 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/lighthouse/providers / POST /api/v1/lighthouse/providers/{id}/connection / Authorization header
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Prowler. Attackers reach the vulnerable code path via POST /api/v1/lighthouse/providers.
Check the vendor advisory for the affected versions of Prowler. Attack surface: POST /api/v1/lighthouse/providers / POST /api/v1/lighthouse/providers/{id}/connection / Authorization header.
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/lighthouse/providers requests with malformed payloads or SQL meta-characters. Run grep -r 'Prowler' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Prowler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Prowlerを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v1/lighthouse/providers' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/lighthouse/providersへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v1/lighthouse/providers on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。