Cyber Resilience

CVE-2026-40113

Praisonai ≤ 4.5.128

Public PoC
Published
09 April 2026
Modified
17 April 2026
Patch / advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-40113 is a high-severity Argument Injection (CWE-88) vulnerability in Praison Praisonai. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-40113 is an argument injection vulnerability (CWE-88) in PraisonAI, a multi-agent teams system, affecting versions prior to 4.5.128. The issue resides in the deploy.py script, which constructs a comma-delimited string for the gcloud run deploy --set-env-vars argument by directly interpolating the openai_model, openai_key, and openai_base values without validating for commas. Since gcloud interprets commas as separators between key-value pairs in --set-env-vars, a comma in any of these values causes the trailing text to be parsed as additional arbitrary KEY=VALUE definitions, enabling injection of unauthorized environment variables into the deployed Cloud Run service. The vulnerability has a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N).

An attacker requires local access to the system running deploy.py, with low privileges (PR:L) and low attack complexity, and no user interaction is needed. By supplying specially crafted values containing commas for openai_model, openai_key, or openai_base—such as during a deployment process—they can inject arbitrary environment variables into the resulting Cloud Run service. This achieves high confidentiality and integrity impacts across a changed scope, potentially allowing control over service behavior, exposure of sensitive data, or modification of runtime configurations.

The GitHub Security Advisory (GHSA-fvxx-ggmx-3cjg) confirms the vulnerability is fixed in PraisonAI version 4.5.128, recommending users upgrade to this or later versions to mitigate the issue.

PraisonAI's integration with OpenAI endpoints highlights relevance to AI/ML deployments on Google Cloud Run, where compromised environment variables could alter model inference or API behaviors. No real-world exploitation has been reported.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

PraisonAI is a multi-agent teams system. Prior to 4.5.128, deploy.py constructs a single comma-delimited string for the gcloud run deploy --set-env-vars argument by directly interpolating openai_model, openai_key, and openai_base without validating that these values do not contain commas. gcloud uses…

more

a comma as the key-value pair separator for --set-env-vars. A comma in any of the three values causes gcloud to parse the trailing text as additional KEY=VALUE definitions, injecting arbitrary environment variables into the deployed Cloud Run service. This vulnerability is fixed in 4.5.128.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34955Same product: Praison Praisonai
CVE-2026-39891Same product: Praison Praisonai
CVE-2026-44334Same product: Praison Praisonai
CVE-2026-40088Same product: Praison Praisonai
CVE-2026-34935Same product: Praison Praisonai
CVE-2026-40156Same product: Praison Praisonai
CVE-2026-40158Same product: Praison Praisonai
CVE-2026-39305Same product: Praison Praisonai
CVE-2026-44338Same product: Praison Praisonai
CVE-2026-39308Same product: Praison Praisonai

Affected Assets

praison
praisonai
≤ 4.5.128

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing can discover argument-injection flaws in command-construction code but does not stop their introduction.

Input validation directly stops construction of command strings containing unneutralized delimiters or injected arguments.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and command construction to prevent argument injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect argument injection but does not prevent it at the source.

prevents

Secure development lifecycle mandates input validation and command construction practices that directly prevent argument injection.

prevents

Application security requirements include explicit rules for safe command-line argument handling and escaping.

prevents

Secure architecture principles discourage unsafe command invocation patterns and favor safer APIs.

prevents

Secure coding standards explicitly require proper neutralization of command arguments, directly eliminating CWE-88.

none

Change management can catch unsafe command patterns during reviews but is not a direct mitigation.

References