CVE-2026-73263: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in prowler-cloud prowler
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.
AI Analysis
Technical Summary
The vulnerability arises from improper neutralization of special elements in the kubeconfig_content used by prowler's Kubernetes provider connection test. Specifically, the legacy gcp auth-provider config allows commands specified in config.cmd-path and config.cmd-args to be executed via subprocess.Popen in the kubernetes-python CommandTokenSource.token method. The check for exec blocks was insufficient, enabling attacker-supplied commands to run on the shared worker environment. This flaw is addressed in prowler version 5.36.0.
Potential Impact
Successful exploitation allows an attacker with at least limited privileges (PR:L) to execute arbitrary OS commands remotely without user interaction, resulting in complete confidentiality, integrity, and availability compromise of the affected system. Given the shared worker context, this could lead to broader impact across multiple users or services relying on the same infrastructure.
Mitigation Recommendations
A patch is available in prowler version 5.36.0 that fixes this vulnerability by properly handling legacy gcp auth-provider configurations and preventing execution of attacker-supplied commands. Users should upgrade to version 5.36.0 or later to remediate this issue. Since this is a cloud service, the vendor manages remediation for the hosted environment; users should verify with the vendor that their environment is updated.
CVE-2026-73263: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in prowler-cloud prowler
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.
CVSS v3.1
Score 9.9critical
Affected software
pkg:github/prowler-cloud/prowlerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from improper neutralization of special elements in the kubeconfig_content used by prowler's Kubernetes provider connection test. Specifically, the legacy gcp auth-provider config allows commands specified in config.cmd-path and config.cmd-args to be executed via subprocess.Popen in the kubernetes-python CommandTokenSource.token method. The check for exec blocks was insufficient, enabling attacker-supplied commands to run on the shared worker environment. This flaw is addressed in prowler version 5.36.0.
Potential Impact
Successful exploitation allows an attacker with at least limited privileges (PR:L) to execute arbitrary OS commands remotely without user interaction, resulting in complete confidentiality, integrity, and availability compromise of the affected system. Given the shared worker context, this could lead to broader impact across multiple users or services relying on the same infrastructure.
Mitigation Recommendations
A patch is available in prowler version 5.36.0 that fixes this vulnerability by properly handling legacy gcp auth-provider configurations and preventing execution of attacker-supplied commands. Users should upgrade to version 5.36.0 or later to remediate this issue. Since this is a cloud service, the vendor manages remediation for the hosted environment; users should verify with the vendor that their environment is updated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-11T17:18:01.599Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a7c89c6bf8831d539b3d5db
Added to database: 08/12/2026, 14:57:10 UTC
Last enriched: 08/12/2026, 15:11:23 UTC
Last updated: 08/12/2026, 16:12:46 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.