CVE-2026-73263 Prowler: RCE on Prowler App workers via kubeconfig auth-provider cmd-path
Attackers can execute arbitrary commands on Prowler App workers by submitting a malicious kubeconfig with a legacy GCP auth-provider.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-73263?
CVE-2026-73263 is a critical command injection vulnerability in prowler-cloud prowler, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-78
Which versions are affected by CVE-2026-73263?
How do I fix CVE-2026-73263?
No fix has been published for CVE-2026-73263 yet. Limit exposure of the affected software until one is available.
Upgrade, and pass arguments to programs as a list instead of through a shell. More about Command injection.
Is CVE-2026-73263 being exploited?
There is no known exploitation of CVE-2026-73263 in the wild and no public exploit code.
Sources
Also known as GHSA-ccqh-6cjc-wp4j.