PraisonAI is a multi-agent teams system. Prior to version 4.6.40, hidden metadata in a webpage causes PraisonAI agents to write attacker-controlled content to arbitrary paths. write_file skips path validation when workspace=None (always None in production). Version 4.6.40 fixes the issue.
CVE-2026-47397
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 48(Track)EG Risk 48/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
May 29, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 21, 2026Arbitrary File Write in Python API · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-hvhp-v2gc-268qrefactor: security batch — 10 hardening fixes
Patch available: MervinPraison/PraisonAI v4.6.126 (PR #1684 merged 2026-05-19)
https://github.com/MervinPraison/PraisonAI/pull/1684commit b0d8f777528f (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.126 (contains commit b0d8f777528f)
https://github.com/MervinPraison/PraisonAI/commit/b0d8f777528f3253a0cfb0a3ef65455da6ae32f6Vendor Advisories for CVE-2026-47397(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonai | 0.0.1 ... 4.6.9 (731 versions) | 4.6.40 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-27 03:11 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 07:37 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 16:29 UTCEG score recompute▲ 7.10
- 2026-07-21 16:28 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-29 23:13 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-47397?
When was CVE-2026-47397 disclosed?
Is CVE-2026-47397 actively exploited?
What is the CVSS score of CVE-2026-47397?
How do I remediate CVE-2026-47397?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47397
Is Your Infrastructure Affected by CVE-2026-47397?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.