CVE-2026-73263

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st 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

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

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Prowler is a cloud security platform. Prior to 5.36.0, the Kubernetes provider connection test accepted kubeconfig_content containing a legacy gcp auth-provider with config.cmd-path and config.cmd-args because kubeconfig_contains_exec_auth in api/src/backend/api/v1/serializers.py checked only exec blocks, and POST /api/v1/providers/{id}/connection loaded it through config.load_kube_config_from_dict in prowler/providers/kubernetes/kubernetes_provider.py, causing kubernetes-python CommandTokenSource.token to run the attacker-supplied command through subprocess.Popen on the shared worker. This issue is fixed in version 5.36.0.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
51st
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: 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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 (4)

Auto-updated Nov 9, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

RCE on Prowler App workers via kubeconfig auth-provider cmd-path · Advisory · prowler-cloud/prowler · GitHub

https://github.com/prowler-cloud/prowler/security/advisories/GHSA-ccqh-6cjc-wp4j
GitHub release Patch Available

Prowler 5.36.0

Patch available: prowler-cloud/prowler 5.36.0

https://github.com/prowler-cloud/prowler/releases/tag/5.36.0
GitHub pull request

fix(kubernetes): block kubeconfig command auth bypass

Fix merged in prowler-cloud/prowler PR #12091 on 2026-07-24 — awaiting tagged release

https://github.com/prowler-cloud/prowler/pull/12091
GitHub commit

commit 0b782fcb8c24 (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit 0b782fcb8c24 — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/0b782fcb8c24ece7bd38deede2b8f13d8583e39c

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 174 rows 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. None are among the latest 100 rows. The 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-73263?
CVE-2026-73263 is a critical-severity vulnerability; its CVE record was published on August 12, 2026. Prowler is a cloud security platform. Prior to 5.36.0, the Kubernetes provider connection test accepted kubeconfig_content containing a legacy gcp auth-provider with config.cmd-path and config.cmd-args because kubeconfig_contains_exec_auth in api/src/backend/api/v1/serializers.py checked only exec…
When was the CVE record for CVE-2026-73263 published?
The CVE record for CVE-2026-73263 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-73263 actively exploited?
CVE-2026-73263 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73263?
CVE-2026-73263 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73263?
A fix for CVE-2026-73263 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-73263

Explore →

Is Your Infrastructure Affected by CVE-2026-73263?

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