CVE-2026-73263

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.9(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity99% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch 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_pr

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 12× in last 7d / 37× 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.

  1. 2026-08-30 04:07 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 08:38 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 14:50 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 18:49 UTCEG score recompute
  8. 2026-08-26 14:47 UTCEPSS rescore
  9. 2026-08-25 15:16 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 17:18 UTCEG score recompute
  12. 2026-08-24 12:32 UTCEG score recompute
  13. 2026-08-23 03:36 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 02:02 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 00:07 UTCEG score recompute
  18. 2026-08-20 22:56 UTCEPSS rescore
  19. 2026-08-19 18:37 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 15:44 UTCEG score recompute
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-17 13:50 UTCEG score recompute
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 12 more
  1. 2026-08-16 15:41 UTCEG score recompute
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 04:44 UTCEG score recompute
  5. 2026-08-16 02:15 UTCEPSS rescore
  6. 2026-08-15 03:00 UTCEG score recompute
  7. 2026-08-15 01:31 UTCEPSS rescore
  8. 2026-08-14 01:26 UTCEG score recompute
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 15:25 UTCEG score recompute
  11. 2026-08-12 14:48 UTCEG score recompute
  12. 2026-08-12 14:48 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73263?
CVE-2026-73263 is a critical vulnerability 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 CVE-2026-73263 disclosed?
CVE-2026-73263 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73263 actively exploited?
CVE-2026-73263 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2026-73263?
CVE-2026-73263 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-73263?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73263, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs