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.
CVE-2026-73264
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity76% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 12, 2026
Advisory Details (7)
Auto-updated Aug 12, 2026Prowler 5.34.0
Patch available: prowler-cloud/prowler 5.34.0
https://github.com/prowler-cloud/prowler/releases/tag/5.34.0Prowler 5.33.1
Patch available: prowler-cloud/prowler 5.33.1
https://github.com/prowler-cloud/prowler/releases/tag/5.33.1commit 3f2e5929d9ff (prowler-cloud/prowler)
Fix landed in prowler-cloud/prowler commit 3f2e5929d9ff — awaiting tagged release
https://github.com/prowler-cloud/prowler/commit/3f2e5929d9ff3c1a5d2fae49f8edd419ee99a8e2commit 1c4d8e3e756e (prowler-cloud/prowler)
Fix landed in prowler-cloud/prowler commit 1c4d8e3e756e — awaiting tagged release
https://github.com/prowler-cloud/prowler/commit/1c4d8e3e756ee04367353101af797004d1c0258ffix(api): harden Lighthouse provider base URLs
Fix merged in prowler-cloud/prowler PR #11940 on 2026-07-10 — awaiting tagged release
https://github.com/prowler-cloud/prowler/pull/11940fix(api): harden Lighthouse provider base URLs
Fix merged in prowler-cloud/prowler PR #11928 on 2026-07-10 — awaiting tagged release
https://github.com/prowler-cloud/prowler/pull/11928Server-Side Request Forgery (SSRF) in Lighthouse Provider · Advisory · prowler-cloud/prowler · GitHub
https://github.com/prowler-cloud/prowler/security/advisories/GHSA-fhj4-q47f-w7mvWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 08:38 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 00:51 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 23:09 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 21:47 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:20 UTCEG score recompute
- 2026-08-23 06:20 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:57 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 03:34 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 02:12 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 00:51 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 23:24 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 22:03 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
Show 10 moreShow fewer
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 09:22 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 08:01 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 06:36 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 15:25 UTCEG score recompute
- 2026-08-12 14:48 UTCEG score recompute
- 2026-08-12 14:48 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-73264?
When was CVE-2026-73264 disclosed?
Is CVE-2026-73264 actively exploited?
What is the CVSS score of CVE-2026-73264?
How do I remediate CVE-2026-73264?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73264
Is Your Infrastructure Affected by CVE-2026-73264?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.