What is the CVSS score of CVE-2026-73263?

CVE-2026-73263 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.4%.

Which versions of Prowler are affected by CVE-2026-73263?

Prowler versions before 5.36.0 are vulnerable to a critical command injection flaw that allows authenticated users with provider-management permissions to execute arbitrary code on backend…. A patch is available.

How to fix or mitigate CVE-2026-73263?

Within 24 hours, audit all Prowler instances to identify versions before 5.36.0, review access logs for suspicious provider-management activity, and document which systems have high-privileged user access. Within 7 days, upgrade all affected Prowler instances to version 5.36.0 or later and perform post-deployment verification. Within 30 days, implement least-privilege access controls for provider-management permissions, conduct a comprehensive audit of who accessed this functionality before patching, and establish ongoing monitoring for unauthorized backend command execution attempts.

Prowler CVE-2026-73263

EUVD-2026-57224 CRITICAL

OS Command Injection (CWE-78)

2026-08-12 GitHub_M

Python Kubernetes Command Injection Prowler Prowler Cloud

9.9

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

vuln.today AI

9.9 CRITICAL

Network API reachable with only low-privilege authenticated provider access (PR:L), trivial to trigger (AC:L), and code runs on a shared worker crossing trust boundaries (S:C) with full RCE impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Aug 12, 2026 - 16:02 EUVD

Source Code Evidence Fetched

Aug 12, 2026 - 15:16 vuln.today

Analysis Generated

Aug 12, 2026 - 15:16 vuln.today

CVE Published

Aug 12, 2026 - 14:26 cve.org

CRITICAL 9.9

DescriptionCVE.org

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.

Articles & Coverage 3

News 3 New Kubernetes Vulnerabilities - 1 Critical, 2 High Severity Aug 13, 2026 News 5 New Python Vulnerabilities - 1 Critical, 4 High, 2 With POC Aug 13, 2026 News Critical Command Injection in Kubernetes Provider (Prowler) - CVE-2026-73263 Aug 12, 2026

AnalysisAI

Authenticated command injection in Prowler (Cloud/API) before 5.36.0 lets a low-privileged user with provider-management access run arbitrary shell commands on the shared backend worker. The Kubernetes provider's connection test accepted a kubeconfig containing a legacy GCP auth-provider with cmd-path/cmd-args, which the kubernetes-python client executed via subprocess when POST /api/v1/providers/{id}/connection loaded it. No public exploit is identified at time of analysis, but the flaw is fixed in 5.36.0 and carries a critical 9.9 CVSS.

Technical ContextAI

Prowler is an open-source cloud/Kubernetes security-posture platform whose API backend (Django REST Framework) validates user-supplied kubeconfig content before establishing provider connections. The root cause is CWE-78 (OS Command Injection): the validator kubeconfig_contains_exec_auth in api/src/backend/api/v1/serializers.py inspected only modern 'exec' credential blocks and ignored the deprecated Kubernetes client-go 'auth-provider' mechanism. When kubeconfig_content is passed to config.load_kube_config_from_dict in prowler/providers/kubernetes/kubernetes_provider.py, the kubernetes-python client's CommandTokenSource.token() invokes the auth-provider's config.cmd-path (with cmd-args) through subprocess.Popen to fetch a token, so any attacker-controlled cmd-path (e.g. /bin/sh) is executed on the worker performing the connection test.

RemediationAI

Upgrade to Prowler 5.36.0 or later, which is the vendor-released patch (Vendor-released patch: 5.36.0); the fix rejects legacy auth-provider.config.cmd-path command authentication in kubeconfig validation (PR https://github.com/prowler-cloud/prowler/pull/12091, commit 0b782fcb8c24ece7bd38deede2b8f13d8583e39c, advisory GHSA-ccqh-6cjc-wp4j). If you cannot upgrade immediately, restrict who can create or run connection tests on Kubernetes providers to trusted administrators only, and pre-screen or reject any kubeconfig_content that contains an 'auth-provider' block with a 'cmd-path'/'cmd-args' (in addition to 'exec' blocks) before it reaches the API - trade-off: this blocks legitimate GCP legacy-auth kubeconfigs, so affected users must switch to supported credential methods. As defense in depth, run connection-test workers with least privilege and constrained network egress so a successful injection has minimal reach.