CVE-2026-48169

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.3%, top 83% 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: 0%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 is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires min_role="member", which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls workspace_id from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The require_workspace_member() dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch 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
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 29, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

advisory-database/vulns/praisonai-platform/PYSEC-2026-2935.yaml at main · pypa/advisory-database · GitHub

https://github.com/pypa/advisory-database/tree/main/vulns/praisonai-platform/PYSEC-2026-2935.yaml
github Patch Available🟡 PoC Available

Cross-Workspace IDOR and Privilege Escalation in Platform API · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gv23-xrm3-8c62

Vendor Advisories for CVE-2026-48169(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 / 38× 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:09 UTCEG score recompute
  11. 2026-08-23 14:04 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 23:32 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-17 06:50 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 05:55 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 02:40 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 20 more
  1. 2026-08-14 00:32 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 22:24 UTCEG score recompute
  4. 2026-08-12 13:51 UTCEPSS rescore
  5. 2026-08-11 15:25 UTCEG score recompute
  6. 2026-08-11 02:22 UTCEG score recompute
  7. 2026-08-11 01:28 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-09 13:49 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-09 00:46 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 22:33 UTCEG score recompute
  14. 2026-07-31 05:51 UTCEG score recompute
  15. 2026-07-27 03:11 UTCEG score recompute
  16. 2026-07-23 03:18 UTCEG score recompute
  17. 2026-06-14 23:18 UTCEPSS rescore
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-05-29 23:13 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48169?
CVE-2026-48169 is a high vulnerability published on May 29, 2026. PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any…
When was CVE-2026-48169 disclosed?
CVE-2026-48169 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48169 actively exploited?
CVE-2026-48169 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 82.5% of all scored CVEs.
What is the CVSS score of CVE-2026-48169?
CVE-2026-48169 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-48169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48169, 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-48169

Explore →

Is Your Infrastructure Affected by CVE-2026-48169?

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

Start Free Scan →Browse All CVEs