CVE-2026-40113
8.4MervinPraison · PraisonAI
PraisonAI is vulnerable to command argument injection because it fails to sanitize inputs for the gcloud run deploy command, allowing attackers to inject arbitrary environment variables into Cloud Run.
Executive summary
A high-severity argument injection vulnerability in PraisonAI allows local attackers with low privileges to manipulate environment variables during service deployment, leading to potential unauthorized configuration.
Vulnerability
This is an improper neutralization of argument delimiters (CWE-88) occurring in the deploy.py script. The application fails to validate that the openai_model, openai_key, and openai_base parameters do not contain commas, allowing a local authenticated attacker to inject arbitrary key-value pairs into the gcloud run deploy command.
Business impact
Successful exploitation of this vulnerability permits the injection of arbitrary environment variables into a deployed Cloud Run service. This can lead to unauthorized access to cloud resources, potential leakage of sensitive credentials, or redirection of application traffic. With a CVSS score of 8.4, the risk is significant due to the potential for total impact on the confidentiality and integrity of the cloud deployment.
Remediation
Immediate Action: Update the PraisonAI package to version 4.5.128 or later via PyPI to incorporate the input validation fix.
Proactive Monitoring: Review application deployment logs and infrastructure configuration changes for unexpected environment variable definitions or unauthorized modifications to the gcloud deployment process.
Compensating Controls: Ensure that the service account executing the deployment process adheres to the principle of least privilege, restricting its ability to modify critical infrastructure configurations beyond what is strictly necessary for deployment.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Given the potential for environment variable injection and the existence of a proof-of-concept, users must prioritize upgrading to version 4.5.128 immediately. Failure to update leaves the deployment pipeline exposed to configuration manipulation that could result in severe security compromises within the cloud environment.