CVE-2026-47399

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Prior to version 0.1.4, the workspace-scoped REST routes contain a systemic object-level authorization flaw that allows an authenticated user from one workspace to access, modify, and delete objects belonging to another workspace by supplying the victim object's global UUID. The affected pattern appears in workspace-scoped routes such as agents, projects, issues, and comments. The route layer verifies that the caller is a member of the workspace_id provided in the URL, but the service layer later resolves the target object by global object ID only. It does not verify that the resolved object actually belongs to the workspace in the URL. As a result, a valid member of workspace_attacker can call a route under /api/v1/workspaces/{workspace_attacker}/... while supplying an object UUID from workspace_victim. The server authorizes the request based on membership in workspace_attacker, then fetches or mutates the victim object by global UUID. This breaks the platform's workspace isolation boundary. PraisonAI Platform version 0.1.4 patches the issue.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/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 computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github, github_commit.
github Patch Available🟡 PoC Available

PraisonAI Platform workspace-scoped routes allow cross-workspace object access by global object ID · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-6h6v-6m7w-7vxx
github_pr Patch Available

refactor: security batch 3 — platform service scoping (do not auto-merge)

Patch available: MervinPraison/PraisonAI v4.6.126 (PR #1686 merged 2026-05-19)

https://github.com/MervinPraison/PraisonAI/pull/1686
github_commit Patch Available

commit 24385d648765 (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.126 (contains commit 24385d648765)

https://github.com/MervinPraison/PraisonAI/commit/24385d64876577620f749957bd4814f162f4ca47

Vendor Advisories for CVE-2026-47399(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)
PackageVulnerable rangeFixed inDependents
praisonai-platform0.1.0, 0.1.1, 0.1.2, 0.1.30.1.4—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 39× 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-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:08 UTCEG score recompute
  11. 2026-08-23 14:03 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 14:59 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 10:24 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 16:06 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 04:21 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 16:52 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 40 more
  1. 2026-08-14 00:27 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 21:39 UTCEG score recompute
  4. 2026-08-12 13:51 UTCEPSS rescore
  5. 2026-08-11 22:39 UTCEG score recompute
  6. 2026-08-11 11:10 UTCEG score recompute
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-09 17:02 UTCEG score recompute
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 18:03 UTCEG score recompute
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 18:44 UTCEG score recompute
  13. 2026-08-06 19:44 UTCEG score recompute
  14. 2026-08-06 13:47 UTCEPSS rescore
  15. 2026-08-05 20:41 UTCEG score recompute
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-04 22:58 UTCEG score recompute
  18. 2026-08-04 15:10 UTCEPSS rescore
  19. 2026-08-04 10:39 UTCEPSS rescore
  20. 2026-08-02 12:53 UTCEG score recompute
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 13:53 UTCEG score recompute
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-31 05:51 UTCEG score recompute
  25. 2026-07-30 16:28 UTCEPSS rescore
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 11:32 UTCEG score recompute
  28. 2026-07-28 15:37 UTCEPSS rescore
  29. 2026-07-28 04:01 UTCEG score recompute
  30. 2026-07-27 03:11 UTCEG score recompute
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-24 14:18 UTCEPSS rescore
  34. 2026-07-23 14:18 UTCEPSS rescore
  35. 2026-07-23 03:17 UTCEG score recompute
  36. 2026-07-22 14:08 UTCEPSS rescore
  37. 2026-06-14 23:18 UTCEPSS rescore
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-12 23:12 UTCEPSS rescore
  40. 2026-05-29 23:13 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47399?
CVE-2026-47399 is a high vulnerability published on May 29, 2026. PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Prior to version 0.1.4, the workspace-scoped REST routes contain a systemic object-level authorization flaw that allows an authenticated user from one workspace to access, modify, and delete objects belonging to…
When was CVE-2026-47399 disclosed?
CVE-2026-47399 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47399 actively exploited?
CVE-2026-47399 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.7% of all scored CVEs.
What is the CVSS score of CVE-2026-47399?
CVE-2026-47399 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-47399?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47399, 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-47399

Explore →

Is Your Infrastructure Affected by CVE-2026-47399?

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

Start Free Scan →Browse All CVEs