CVE-2026-48169

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 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
37th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-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-17). 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

September 18, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
praisonai-platform0.1.0, 0.1.1, 0.1.2, 0.1.3
  • every version up to 0.1.4: fixed in 0.1.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 32× 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.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-18 03:35 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-17 12:28 UTCEG score recompute
  6. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-12 16:01 UTCEG score recompute
  12. 2026-10-11 19:44 UTCEG score recompute
  13. 2026-10-11 16:58 UTCEG score recompute
  14. 2026-10-11 14:23 UTCEG score recompute
  15. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-08 14:54 UTCOSV refresh
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 64 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-09-18 20:36 UTCEG score recompute
  9. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-09-14 06:17 UTCEG score recompute
  13. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-09-13 01:06 UTCOSV refresh
  15. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-08-25 04:09 UTCEG score recompute
  30. 2026-08-23 14:04 UTCEG score recompute
  31. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-08-20 23:32 UTCEG score recompute
  34. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-08-20 10:24 UTCEG score recompute
  36. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-08-17 06:50 UTCEG score recompute
  40. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-08-16 05:55 UTCEG score recompute
  42. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-08-15 02:40 UTCEG score recompute
  44. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-08-14 00:32 UTCEG score recompute
  46. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-08-12 22:24 UTCEG score recompute
  48. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-11 15:25 UTCEG score recompute
  50. 2026-08-11 02:22 UTCEG score recompute
  51. 2026-08-11 01:28 UTCEG score recompute
  52. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-09 13:49 UTCEG score recompute
  54. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-09 00:46 UTCEG score recompute
  56. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-08-07 22:33 UTCEG score recompute
  58. 2026-07-31 05:51 UTCEG score recompute
  59. 2026-07-27 03:11 UTCEG score recompute
  60. 2026-07-23 03:18 UTCEG score recompute
  61. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 13th percentile
  62. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 13th percentile
  63. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 13th percentile
  64. 2026-05-29 23:13 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-48169?
CVE-2026-48169 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-48169 published?
The CVE record for CVE-2026-48169 was published on May 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-48169 actively exploited?
CVE-2026-48169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48169?
CVE-2026-48169 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48169?
A fix for CVE-2026-48169 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48169 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs