Is CVE-2026-48169 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48169 being exploited in the wild.

How severe is CVE-2026-48169?

High severity, with a CVSS score of 8.8, published 7 August 2026.

Which products and versions are affected?

praisonai-platform (PyPI) <= 0.1.2, ECOSYSTEM:introduced=0,fixed=0.1.4.

Is there a fix for CVE-2026-48169?

Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48169 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48169?

Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48169: PraisonAI Platform IDOR and privilege escalation in Platform API

Q: Is there a fix for CVE-2026-48169?

Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48169 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-48169?

Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48169 · Severity: high · CVSS 8.8 · Published 2026-08-07

PraisonAI Platform, a tool for managing AI projects and workspaces, contains security flaws that allow any registered user to access or modify data belonging to other organizations. Additionally, a low-privileged member of a workspace can exploit these flaws to promote themselves to an administrator and lock out the original owners. This could lead to a total loss of data privacy and unauthorized control over corporate AI projects.

Technologies: praisonai-platform (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-48169 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48169 being exploited in the wild.
How severe is CVE-2026-48169?: High severity, with a CVSS score of 8.8, published 7 August 2026.
Which products and versions are affected?: praisonai-platform (PyPI) <= 0.1.2, ECOSYSTEM:introduced=0,fixed=0.1.4.
Is there a fix for CVE-2026-48169?: Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48169 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48169?: Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

praisonai-platform (PyPI): upgrade to 0.1.4 or later
```
pip install "praisonai-platform>=0.1.4"
```

Technical details

The PraisonAI Platform API suffers from two primary authorization failures. First, the service layer for 'issues' and 'projects' (e.g., issue_service.py) performs global database lookups using primary keys without verifying workspace ownership, enabling cross-workspace IDOR. An attacker can read, update, or delete resources in any workspace by manipulating UUIDs in API requests. Second, member management endpoints in workspaces.py only require a 'member' role for access and lack server-side checks for role hierarchy or self-promotion. This allows any workspace member to escalate their privileges to 'owner' and remove other members, including the original creator. These issues are addressed in version 0.1.4.

Affected products

MervinPraison praisonai-platform <= 0.1.2

Identifiers

CVE-2026-48169
GHSA-gv23-xrm3-8c62
PYSEC-2026-2935

Timeline

2026-05-19: advisory: Initial disclosure on GitHub
2026-05-29: patched: Updated advisory and patch availability confirmed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.