ZeroDay Findings
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-61442

PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass

Published Oct 8, 2026 · catalog updated Oct 15, 2026 · PraisonAI: Platform member PATCH

Check if you run it

No confirmed exploitation is on record for CVE-2026-61442. EPSS is 0.46%. Act only if a listed version of PraisonAI: Platform member PATCH is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (PraisonAI: Platform member PATCH).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.46%
Remediation
Advisory link
Affected products
PyPI praisonai-platform

# Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned before the reassignment. ## Technical Details The affected boundary is the difference between "is a workspace member" and "owns or administers this resource". defines , , , and . only checks that the caller has at least the role in the workspace, while allows delete only for workspace admins/owners or the resource owner. The project update route in defines with . It passes , , , , and into . then writes when supplied. The paired project delete route first loads the project and calls . This means an ordinary member can mutate the ownership field that the delete route later trusts. The same update/delete asymmetry exists for issues and agents. defines with only , validates referenced ids are in the workspace, then calls to write fields including , , , , , and . The paired delete route checks . defines with only and calls to write fields including , , and ; the paired delete route checks . The intended owner/admin boundary is visible from the delete routes and from the local negative controls: a workspace member cannot directly delete an owner-created project, issue, or agent, and a non-member cannot patch an issue. The vulnerability is that the PATCH routes do not apply an equivalent owner/admin or resource-specific update guard. ## PoV the PoV starts an in-memory FastAPI app backed by SQLite, creates an owner, a member, and an outsider, adds the member to the owner's workspace, then exercises the project, issue, and agent routes without touching any live service. Essential excerpt: The full PoV script is included in the appendix below as . ## Po

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI praisonai-platform0 → 0.1.9

How to fix CVE-2026-61442

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-61442. EPSS is 0.46%. Act only if a listed version of PraisonAI: Platform member PATCH is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.1.9. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-862: Missing Authorization; CWE-863: Incorrect Authorization. EPSS 0.46%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · GitHub Advisory Database

    Detected

    # Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch to their own user id and then delete the owner-created project, bypassing a delete

  2. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    praisonai-platform fixed in 0.1.9

  3. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    praisonai-platform fixed in 0.1.9

  4. Oct 8, 2026 · GitHub Advisory Database

    Updated

    # Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch to their own user id and then delete the owner-created project, bypassing a delete

  5. Oct 15, 2026 · GitHub Advisory Database

    Updated

    # Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch to their own user id and then delete the owner-created project, bypassing a delete

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.