PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Prior to version 0.1.4, the Platform server exposes resources under /api/v1/workspaces/{workspace_id}/... and protects them with a require_workspace_member(workspace_id) FastAPI dependency. The dependency only checks that the caller is a member of the workspace_id in the URL prefix. The route handlers then look up the inner resource (agent_id, issue_id, project_id, label_id, comment_id, dependency_id) by primary key alone. The resource's own workspace_id is never compared to the URL's workspace_id. A user can therefore put their own workspace in the URL prefix and any other workspace's resource ID in the path. The auth check passes, since they really are a member of the prefix workspace. The service then returns the cross-tenant resource for read, update, or delete. There is a second bug in the member-management routes (add_member, update_member_role, remove_member, update_workspace, delete_workspace). Each one inherits the default min_role="member" from require_workspace_member. Any basic member can therefore promote themselves to admin or owner, demote or remove other members, and delete the workspace. The role hierarchy exists in the schema but is not enforced. Registration is open at /api/v1/auth/register with no email verification. The default server bind is 0.0.0.0:8000 (python -m praisonai_platform). One curl from any unauthenticated network position is enough to bootstrap into the system. PraisonAI Platform version 0.1.4 patches the issue.
CVE-2026-47407
“—” beside the score: it is equal to the CVSS score beside it.
This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 9.4
- EG Score
- 9.4CRITICALmedium confidence
- EG Risk
- 58EG Risk 58/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity94% × 45%Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 34th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 29, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Oct 2, 2026Cross-workspace IDOR + member-role privilege escalation in PraisonAI Platform · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-h8q5-cp56-rr65refactor: security batch 3 — platform service scoping (do not auto-merge)
Patch available: MervinPraison/PraisonAI v4.6.148 (PR #1686 merged 2026-05-19)
https://github.com/MervinPraison/PraisonAI/pull/1686commit 24385d648765 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.148 (contains commit 24385d648765)
https://github.com/MervinPraison/PraisonAI/commit/24385d64876577620f749957bd4814f162f4ca47Vendor Advisories for CVE-2026-47407(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 | Fix by version range | Dependents |
|---|---|---|---|
| praisonai-platform | 0.1.0, 0.1.1, 0.1.2, 0.1.3 |
| — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 37× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 117 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-19 11:31 UTCEG score recompute
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 03:36 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-17 07:45 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-16 07:30 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 06:24 UTCEG score recompute
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-14 02:04 UTCEG score recompute
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 22:22 UTCEG score recompute
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 16:01 UTCEG score recompute
- 2026-10-11 19:44 UTCEG score recompute
- 2026-10-11 16:59 UTCEG score recompute
- 2026-10-11 14:24 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 75 moreShow fewer
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-03 14:09 UTCOSV refresh
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-14 06:17 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-13 01:06 UTCOSV refresh
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-25 04:08 UTCEG score recompute
- 2026-08-23 14:04 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-22 00:33 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-21 02:24 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-20 10:24 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-16 15:02 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-16 02:23 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-15 16:52 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-14 00:27 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-12 17:54 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-11 16:04 UTCEG score recompute
- 2026-08-11 03:45 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-09 15:08 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-08 18:39 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-07 18:02 UTCEG score recompute
- 2026-08-06 17:09 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-05 20:41 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-04 22:58 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-02 06:42 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-01 13:53 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-07-31 05:51 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:praisonai-platform
Frequently asked(5)
What is CVE-2026-47407?
When was the CVE record for CVE-2026-47407 published?
Is CVE-2026-47407 actively exploited?
What is the CVSS score of CVE-2026-47407?
How do I remediate CVE-2026-47407?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47407
Is Your Infrastructure Affected by CVE-2026-47407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.