CVE-2026-47415

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: 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. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The issue CRUD endpoints (GET / PATCH / DELETE /workspaces/{workspace_id}/issues/{issue_id}) gate access on require_workspace_member(workspace_id) only, then resolve issue_id through IssueService.get(issue_id) which is a primary-key lookup with no workspace constraint. A user who is a member of any workspace W1 can read, modify, or delete issues that belong to a different workspace W2. PraisonAI Platform version 0.1.4 patches the issue.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track*)
EG Risk 53/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
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
Patch available. Sources: github_commit, github.
github Patch Available

praisonai-platform: Issue endpoints accept any issue_id without workspace ownership check, cross-workspace read/update/delete IDOR · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-xwq8-frcg-77q8
github_commit Patch Available

commit ef79b7a05617 (MervinPraison/PraisonAI)

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

https://github.com/MervinPraison/PraisonAI/commit/ef79b7a0561796ad9807f0f09538c25cc78d3619

Vendor Advisories for CVE-2026-47415(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(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47415?
CVE-2026-47415 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 issue CRUD endpoints (GET / PATCH / DELETE /workspaces/{workspaceid}/issues/{issueid}) gate access on requireworkspacemember(workspaceid) only,…
When was CVE-2026-47415 disclosed?
CVE-2026-47415 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-47415 actively exploited?
CVE-2026-47415 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.4% of all scored CVEs.
What is the CVSS score of CVE-2026-47415?
CVE-2026-47415 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-47415?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47415, 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-47415

Explore →

Is Your Infrastructure Affected by CVE-2026-47415?

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

Start Free Scan →Browse All CVEs