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% (49th 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
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 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 computed (value × EchelonGraph’s weight)
Severity99% × 45%
The EG Score, 9.9 of 10.
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
49th
KEV
Not listed

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.

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

September 9, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

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 13× in last 7d / 50× 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 97 of 111 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

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 kubeconfigcontent containing a legacy gcp auth-provider with config.cmd-path and config.cmd-args because kubeconfigcontainsexecauth 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 September 9, 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 (49th 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.

Book a Demo →Browse All CVEs