PraisonAI before 4.6.78 fails to safely encode deployment configuration values when generating Python source code for API servers. Attackers can inject arbitrary Python expressions through the deploy.api.host and agents_file configuration parameters that execute when the generated server starts or handles requests.
CVE-2026-61433
HIGHPre-NVD 7.87.8—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic
PraisonAI before 4.6.78 Code Injection via API deployment generator | Advisories | VulnCheck
https://www.vulncheck.com/advisories/praisonai-before-code-injection-via-api-deployment-generatorgithub Patch Available🟡 PoC Available
API deploy code generator embeds unescaped YAML fields into Python source · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-79fv-7hq9-w7xggithub_commit Patch Available
commit 1620b49f3694 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.118 (contains commit 1620b49f3694)
https://github.com/MervinPraison/PraisonAI/commit/1620b49f36945d8cc8ee5635b906c960df5097a0Vendor Advisories for CVE-2026-61433(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 23:47 UTCEG score recompute
- 2026-07-15 23:47 UTCGHSA enrichment
- 2026-07-15 11:55 UTCEG score recompute
- 2026-07-15 11:54 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-61433?
CVE-2026-61433 is a high vulnerability published on July 15, 2026. PraisonAI before 4.6.78 fails to safely encode deployment configuration values when generating Python source code for API servers. Attackers can inject arbitrary Python expressions through the deploy.api.host and agents_file configuration parameters that execute when the generated server starts or…
When was CVE-2026-61433 disclosed?
CVE-2026-61433 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-61433?
CVE-2026-61433 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-61433?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61433, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61433
Is Your Infrastructure Affected by CVE-2026-61433?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.