CVE-2026-61444

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-10. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PraisonAI versions before 4.6.78 contain a code injection vulnerability in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without sanitization. Attackers can inject arbitrary Python code that executes when the generated server code runs via subprocess.Popen().

CVSS v3
9.1
EG Score
9.1(high)
EPSS
31.4%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

PraisonAI before 4.6.78 Code Injection via f-string | Advisories | VulnCheck

https://www.vulncheck.com/advisories/praisonai-before-code-injection-via-f-string
github Patch Available🟡 PoC Available

Code Injection via f-string Interpolation in Deploy API Server Generation · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-g6j7-pffp-8whg

Vendor Advisories for CVE-2026-61444(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 71× in last 7d / 71× 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.

  1. 2026-07-16 01:38 UTCEG score recompute
  2. 2026-07-16 01:38 UTCGHSA enrichment
  3. 2026-07-15 21:25 UTCEG score recompute
  4. 2026-07-15 21:25 UTCGHSA enrichment
  5. 2026-07-15 17:12 UTCEG score recompute
  6. 2026-07-15 17:11 UTCGHSA enrichment
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 12:57 UTCEG score recompute
  9. 2026-07-15 12:57 UTCGHSA enrichment
  10. 2026-07-15 08:40 UTCEG score recompute
  11. 2026-07-15 08:40 UTCGHSA enrichment
  12. 2026-07-15 04:27 UTCEG score recompute
  13. 2026-07-15 04:27 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-15 00:12 UTCEG score recompute
  17. 2026-07-15 00:12 UTCGHSA enrichment
  18. 2026-07-14 19:59 UTCEG score recompute
  19. 2026-07-14 19:59 UTCGHSA enrichment
  20. 2026-07-14 15:46 UTCEG score recompute
  21. 2026-07-14 15:46 UTCGHSA enrichment
  22. 2026-07-14 11:33 UTCEG score recompute
  23. 2026-07-14 11:33 UTCGHSA enrichment
  24. 2026-07-14 07:20 UTCEG score recompute
  25. 2026-07-14 07:19 UTCGHSA enrichment
Show 46 more
  1. 2026-07-14 03:06 UTCEG score recompute
  2. 2026-07-14 03:06 UTCGHSA enrichment
  3. 2026-07-13 22:54 UTCEG score recompute
  4. 2026-07-13 22:54 UTCGHSA enrichment
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 18:41 UTCEG score recompute
  7. 2026-07-13 18:41 UTCGHSA enrichment
  8. 2026-07-13 14:28 UTCEG score recompute
  9. 2026-07-13 14:28 UTCGHSA enrichment
  10. 2026-07-13 10:13 UTCEG score recompute
  11. 2026-07-13 10:13 UTCGHSA enrichment
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 06:00 UTCEG score recompute
  15. 2026-07-13 06:00 UTCGHSA enrichment
  16. 2026-07-13 01:47 UTCEG score recompute
  17. 2026-07-13 01:47 UTCGHSA enrichment
  18. 2026-07-12 21:34 UTCEG score recompute
  19. 2026-07-12 21:34 UTCGHSA enrichment
  20. 2026-07-12 17:21 UTCEG score recompute
  21. 2026-07-12 17:21 UTCGHSA enrichment
  22. 2026-07-12 13:08 UTCEG score recompute
  23. 2026-07-12 13:08 UTCGHSA enrichment
  24. 2026-07-12 08:55 UTCEG score recompute
  25. 2026-07-12 08:55 UTCGHSA enrichment
  26. 2026-07-12 05:46 UTCEPSS rescore
  27. 2026-07-12 04:41 UTCEG score recompute
  28. 2026-07-12 04:41 UTCGHSA enrichment
  29. 2026-07-12 00:28 UTCEG score recompute
  30. 2026-07-12 00:28 UTCGHSA enrichment
  31. 2026-07-11 20:16 UTCEG score recompute
  32. 2026-07-11 20:15 UTCGHSA enrichment
  33. 2026-07-11 16:02 UTCEG score recompute
  34. 2026-07-11 16:02 UTCGHSA enrichment
  35. 2026-07-11 11:49 UTCEG score recompute
  36. 2026-07-11 11:49 UTCGHSA enrichment
  37. 2026-07-11 07:36 UTCEG score recompute
  38. 2026-07-11 07:36 UTCGHSA enrichment
  39. 2026-07-11 03:22 UTCEG score recompute
  40. 2026-07-11 03:22 UTCGHSA enrichment
  41. 2026-07-10 23:09 UTCEG score recompute
  42. 2026-07-10 23:09 UTCGHSA enrichment
  43. 2026-07-10 18:55 UTCEG score recompute
  44. 2026-07-10 18:55 UTCGHSA enrichment
  45. 2026-07-10 14:42 UTCEG score recompute
  46. 2026-07-10 14:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61444?
CVE-2026-61444 is a critical vulnerability published on July 10, 2026. PraisonAI versions before 4.6.78 contain a code injection vulnerability in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without sanitization. Attackers can inject arbitrary Python code that executes when the generated server code runs via…
When was CVE-2026-61444 disclosed?
CVE-2026-61444 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61444 actively exploited?
CVE-2026-61444 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-61444?
CVE-2026-61444 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-61444?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61444, 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-61444

Explore →

Is Your Infrastructure Affected by CVE-2026-61444?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs