CVE-2026-73263: prowler · OS Command Injection
Affects prowlerSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical : upgrade to 5.36.0 as a priority.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.36.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade prowler and prowler-cloud/prowler to 5.36.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| prowler-cloudprowler | Affected
| Fixed in
|
GitHubprowler-cloud/prowlerpkg:github/prowler-cloud/prowlerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.
References
- github.com/prowler-cloud/prowler/security/advisories/GHSA-ccqh-6cjc-wp4j (opens in a new tab)
- github.com/prowler-cloud/prowler/pull/12091 (opens in a new tab)
- github.com/prowler-cloud/prowler/commit/0b782fcb8c24ece7bd38deede2b8f13d8583e39c (opens in a new tab)
- github.com/prowler-cloud/prowler/releases/tag/5.36.0 (opens in a new tab)