CVE-2026-73263: Prowler: RCE on Prowler App workers via kubeconfig auth-provider cmd-path
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.
Security readout for executives and security teams
Plain-English summary
An authenticated user with limited privileges could submit a crafted Kubernetes configuration that makes a Prowler App worker run an attacker-chosen operating-system command. Because workers may be shared, compromise could expose data, alter operations, or disrupt service beyond the initiating user’s scope.
Executive priority
Treat as an immediate remediation priority for affected Prowler App deployments, especially multi-user or shared-worker environments. Upgrade promptly and investigate historical provider connection activity because successful exploitation could compromise confidentiality, integrity, and availability.
Technical view
Before Prowler 5.36.0, validation checked Kubernetes exec authentication but missed legacy GCP auth-provider cmd-path settings. During provider connection testing, kubernetes-python processed that setting and launched the supplied command through subprocess.Popen on the worker. This is CWE-78 command injection with a CVSS 3.1 score of 9.9.
Likely exposure
Prowler deployments below 5.36.0 are potentially exposed when users can submit Kubernetes kubeconfig content and invoke the provider connection test. CVSS indicates network access and low privileges are required, with no user interaction. Internet exposure is not established by the supplied evidence.
Exploitation context
The supplied sources do not report active exploitation, and this CVE is not identified as being in KEV. Exploitation requires authenticated, low-privilege access to the relevant API workflow. Successful exploitation executes commands on a shared application worker, creating possible cross-scope impact.
Researcher notes
The root cause was incomplete unsafe-authentication detection: kubeconfig_contains_exec_auth inspected exec blocks but omitted legacy GCP auth-provider command fields. The vulnerable connection path loaded attacker-controlled configuration through load_kube_config_from_dict, reaching CommandTokenSource and subprocess.Popen. The supplied evidence establishes the flaw and fix, but not real-world exploitation.
Mitigation direction
Upgrade Prowler to version 5.36.0 or later as the primary remediation.
Until upgraded, restrict Kubernetes provider configuration and connection testing to trusted administrators.
Follow the vendor advisory for any additional deployment-specific guidance.
Validation and detection
Inventory Prowler App deployments and confirm every running component is version 5.36.0 or later.
Review stored Kubernetes configurations for legacy GCP auth-provider entries containing cmd-path or cmd-args.
Review worker and API telemetry for unusual processes associated with Kubernetes provider connection tests.
Confirm the upgraded application rejects unsafe legacy command-based authentication configurations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.