PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The comment endpoints (POST /workspaces/{workspace_id}/issues/{issue_id}/comments and GET .../comments) gate access on require_workspace_member(workspace_id) only, then call CommentService.create(issue_id=issue_id, ...) and CommentService.list_for_issue(issue_id) without verifying that issue_id belongs to workspace_id. A user who is a member of any workspace W1 can read every comment on, and post new comments to, any issue in any other workspace W2. PraisonAI Platform version 0.1.4 patches the issue.
CVE-2026-47417
HIGHPre-NVD 8.18.1—Elevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 52(Track)EG Risk 52/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 computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 11.1%
- KEV
- Not listed
Published
June 1, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 21, 2026Patch available. Sources: github_commit, github.
github Patch Available
praisonai-platform: Comment endpoints accept any issue_id without workspace ownership check, cross-workspace comment read and post IDOR · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-cp4f-5m9r-5jc2github_commit Patch Available
commit ef79b7a05617 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.126 (contains commit ef79b7a05617)
https://github.com/MervinPraison/PraisonAI/commit/ef79b7a0561796ad9807f0f09538c25cc78d3619Vendor Advisories for CVE-2026-47417(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-platform | 0.1.0, 0.1.1, 0.1.2, 0.1.3 | 0.1.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-01 14:49 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-47417?
CVE-2026-47417 is a high vulnerability published on June 1, 2026. PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The comment endpoints (POST /workspaces/{workspaceid}/issues/{issueid}/comments and GET .../comments) gate access on…
When was CVE-2026-47417 disclosed?
CVE-2026-47417 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47417 actively exploited?
CVE-2026-47417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47417?
CVE-2026-47417 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-47417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47417, 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
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47417
Is Your Infrastructure Affected by CVE-2026-47417?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.