PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-48169 MervinPraison CVE debrief

CVE-2026-48169 is a high-severity vulnerability in the PraisonAI Platform API, with a CVSS score of 8.8. The vulnerability allows any authenticated user to read, modify, and delete resources in any workspace by swapping UUIDs in their API requests. Additionally, any workspace member can promote themselves to owner and kick out the original owner. The issue is patched in version 0.1.4 of the PraisonAI Platform API.

Vendor
MervinPraison
Product
praisonai-platform
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-07
Original CVE updated
2026-09-18
Advisory published
2026-08-07
Advisory updated
2026-09-18

Who should care

Defenders responsible for PraisonAI Platform API deployments should assess exposure and prioritize patching to version 0.1.4 or later. This includes operators managing the platform, vulnerability management teams, and security teams responsible for verifying workspace isolation and access controls. They should verify affected scope, assess potential impact, and implement compensating controls if necessary.

Why it matters

CVE-2026-48169 allows unauthorized access to workspace resources, enabling data tampering, deletion, and workspace takeover. Defenders should prioritize patching and verify workspace isolation.

  • Unauthorized access to sensitive resources
  • Data tampering and deletion possible
  • Workspace takeover by low-privilege members
  • Verification of workspace isolation and access controls required

Technical summary

The PraisonAI Platform API has two authorization failures that break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, allowing any authenticated user to read, modify, and delete resources in any workspace. Additionally, every member management endpoint only requires `min_role='member'`, allowing any workspace member to promote themselves to owner and kick out the original owner.

Defensive priority

Defenders should prioritize patching to version 0.1.4 or later, verify workspace isolation, and restrict access to sensitive resources.

Recommended defensive actions

  • Patch to version 0.1.4 or later
  • Verify workspace isolation
  • Restrict access to sensitive resources
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. PraisonAI Platform API versions prior to 0.1.4 have two authorization failures that break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, allowing any authenticated user to read, modify, and delete resources in any workspace. Additionally, every member management endpoint only requires `min_role='member'`, allowing any

Sources and references

Verified primary and authoritative sources

  • CVE-2026-48169 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-48169

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-48169 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-48169

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.