Security readout for executives and security teams
Plain-English summary
PraisonAI before 4.6.78 has a critical code injection flaw. A highly privileged attacker who can control the agents_file parameter could cause attacker-supplied Python code to run when PraisonAI generates and launches server code. This creates potential full confidentiality, integrity, and availability impact on affected deployments.
Executive priority
Treat as urgent for any organization using PraisonAI in production or automation. Prioritize patching affected deployments and verifying administrative access controls, while noting there is no provided evidence of active exploitation.
Technical view
The issue is CWE-94 in deploy/api.py. The agents_file parameter is interpolated into an f-string without sanitization, and the resulting generated server code is later executed through subprocess.Popen(). The CVSS 4.0 vector is network reachable, low complexity, no user interaction, high privileges required, with high vulnerable and subsequent system impacts.
Likely exposure
Exposure is limited to environments running MervinPraison PraisonAI versions before 4.6.78, especially where privileged users or automation can invoke the affected deployment API path and supply agents_file values.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The vulnerability is still high urgency because successful abuse can execute arbitrary Python code, but available evidence indicates high privileges are required.
Researcher notes
The key evidence is direct interpolation of agents_file into generated Python code followed by subprocess execution. Analysis should focus on reachable deployment flows, required privilege boundaries, and whether logs can identify suspicious parameter use without reproducing exploit behavior.
Mitigation direction
- Upgrade PraisonAI to 4.6.78 or later.
- Restrict deployment API access to trusted administrators only.
- Review GitHub advisory guidance before applying compensating controls.
- Audit recent PraisonAI deployment activity for unexpected generated code or process launches.
- Rotate credentials exposed to affected PraisonAI hosts if compromise is suspected.
Validation and detection
- Inventory all PraisonAI installations and confirm installed versions.
- Flag any PraisonAI version earlier than 4.6.78 for remediation.
- Review access controls around deploy/api.py and deployment automation.
- Check logs for unusual deployment requests involving agents_file.
- Confirm upgraded systems no longer run vulnerable releases.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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.
Open ATT&CK lookupCVE-2026-61444 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-g6j7-pffp-8whg)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: PraisonAI before 4.6.78 Code Injection via f-stringCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.