CVE-2026-73264

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-57225 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 12, 2026

Last Modified

October 24, 2026

Advisory Details (7)

Auto-updated Aug 12, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Prowler 5.34.0

Patch available: prowler-cloud/prowler 5.34.0

https://github.com/prowler-cloud/prowler/releases/tag/5.34.0
GitHub release Patch Available

Prowler 5.33.1

Patch available: prowler-cloud/prowler 5.33.1

https://github.com/prowler-cloud/prowler/releases/tag/5.33.1
GitHub commit

commit 3f2e5929d9ff (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit 3f2e5929d9ff — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/3f2e5929d9ff3c1a5d2fae49f8edd419ee99a8e2
GitHub commit

commit 1c4d8e3e756e (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit 1c4d8e3e756e — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/1c4d8e3e756ee04367353101af797004d1c0258f
GitHub pull request

fix(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/11940
GitHub pull request

fix(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/11928
GitHub advisoryMentions a patch (unverified)

Server-Side Request Forgery (SSRF) in Lighthouse Provider · Advisory · prowler-cloud/prowler · GitHub

https://github.com/prowler-cloud/prowler/security/advisories/GHSA-fhj4-q47f-w7mv

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 130 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 07:33 UTCEG score recompute
  2. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-10-25 14:06 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-23 20:28 UTCEG score recompute
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-19 08:51 UTCEG score recompute
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-18 03:15 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-10-12 15:39 UTCEG score recompute
Show 73 more
  1. 2026-10-11 19:26 UTCEG score recompute
  2. 2026-10-11 16:42 UTCEG score recompute
  3. 2026-10-11 14:02 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-06 17:30 UTCEG score recompute
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-05 14:49 UTCEG score recompute
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-03 20:14 UTCEG score recompute
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-02 22:01 UTCEG score recompute
  17. 2026-10-02 08:22 UTCEG score recompute
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-09-30 21:58 UTCEG score recompute
  20. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-29 04:51 UTCEG score recompute
  22. 2026-09-28 14:20 UTCEG score recompute
  23. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-09-28 01:34 UTCEG score recompute
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-27 09:56 UTCEG score recompute
  27. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-09-25 03:42 UTCEG score recompute
  29. 2026-09-24 01:50 UTCEG score recompute
  30. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-09-22 23:56 UTCEG score recompute
  32. 2026-09-21 22:35 UTCEG score recompute
  33. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-21 09:52 UTCEG score recompute
  35. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  36. 2026-09-19 16:37 UTCEG score recompute
  37. 2026-09-19 03:49 UTCEG score recompute
  38. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  39. 2026-09-18 02:27 UTCEG score recompute
  40. 2026-09-17 00:23 UTCEG score recompute
  41. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-09-15 13:13 UTCEG score recompute
  44. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-09-14 05:10 UTCEG score recompute
  46. 2026-09-12 15:09 UTCEG score recompute
  47. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-09-12 02:28 UTCEG score recompute
  49. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-09-11 13:48 UTCEG score recompute
  51. 2026-09-10 10:09 UTCEG score recompute
  52. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-09-09 05:18 UTCEG score recompute
  54. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-09-07 18:35 UTCEG score recompute
  56. 2026-09-06 14:49 UTCEG score recompute
  57. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-09-06 02:08 UTCEG score recompute
  59. 2026-09-05 00:44 UTCEG score recompute
  60. 2026-09-04 07:57 UTCEG score recompute
  61. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  62. 2026-09-02 23:39 UTCEG score recompute
  63. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  64. 2026-09-02 01:55 UTCEG score recompute
  65. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  66. 2026-09-01 13:14 UTCEG score recompute
  67. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  68. 2026-08-30 22:40 UTCEG score recompute
  69. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  70. 2026-08-30 09:59 UTCEG score recompute
  71. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  72. 2026-08-29 08:38 UTCEG score recompute
  73. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile

Frequently asked(5)

What is CVE-2026-73264?
CVE-2026-73264 is a high-severity vulnerability; its CVE record was published on August 12, 2026. Prowler is a cloud security platform. Prior to 5.33.1, an authenticated user with Lighthouse provider configuration access could supply an unvalidated baseurl for the openaicompatible provider through POST /api/v1/lighthouse/providers and POST /api/v1/lighthouse/providers/{id}/connection, causing…
When was the CVE record for CVE-2026-73264 published?
The CVE record for CVE-2026-73264 was published on August 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73264 actively exploited?
CVE-2026-73264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73264?
CVE-2026-73264 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73264?
A fix for CVE-2026-73264 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73264

Explore →

Is Your Infrastructure Affected by CVE-2026-73264?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.