dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-61440

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PraisonAI Platform before 0.1.9 fails to properly authorize label and issue-label mutations, allowing workspace members to rename and recolor shared labels and add or remove labels on owner-created issues. Attackers with workspace member privileges can exploit PATCH and POST/DELETE endpoints to alter shared label taxonomy and manipulate issue-label associations without owner or admin authorization.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PraisonAI Platform before 0.1.9 contains an improper authorization vulnerability where workspace members can exploit PATCH and POST/DELETE endpoints to rename and recolor shared labels, and add or remove labels on owner-created issues without proper authorization checks.

MitigationUpgrade to PraisonAI Platform version 0.1.9 or later which implements proper authorization validation for label and issue-label mutation operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify PraisonAI Platform is installed
    Check for the PraisonAI package in your Python environment using 'pip show praisonai' or 'pip list | grep -i praisonai', or look for application files in your deployment directory
    Affected if PraisonAI Platform is not found in your environment
  2. Determine the installed PraisonAI version
    Run 'pip show praisonai' and note the Version field, or check package.json/version file in the application directory if installed from source
    Affected if The version cannot be determined or is below 0.1.9
  3. Compare installed version to affected range
    Compare your installed version number to the affected range: versions before 0.1.9 are vulnerable; version 0.1.9 and later are not
    Affected if Installed version is 0.1.8, 0.1.7, or any version lower than 0.1.9
  4. Confirm vulnerable API endpoints are accessible (optional)
    If running the application, inspect API routes for PATCH/POST/DELETE endpoints handling /labels or /issues/{id}/labels; verify no authorization decorator checks ownership before label mutations
    Affected if Label mutation endpoints exist and accept requests without validating that the requesting user owns the issue or has permission to modify shared labels

You are affected if PraisonAI Platform is installed with a version lower than 0.1.9 and the label mutation API endpoints are accessible without proper authorization validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to PraisonAI Platform version 0.1.9 or later which implements proper authorization validation for label and issue-label mutation operations.

Recommended fix Moderate confidence

Upgrade to PraisonAI Platform version 0.1.9

  1. 1. Identify the current installed version of PraisonAI Platform by checking the package.json, setup.py, or running 'pip show praisonai' or 'praisonai --version'
  2. 2. If the current version is before 0.1.9, back up any critical data and configurations
  3. 3. Upgrade PraisonAI Platform to version 0.1.9 using the appropriate package manager: 'pip install praisonai==0.1.9' or 'pip install --upgrade praisonai'
  4. 4. Alternatively, if using a containerized deployment, update the image tag to the version containing the fix
  5. 5. Verify the upgrade was successful by checking the installed version
  6. 6. Test that authorization controls now properly restrict label mutations to owners and admins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61440 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data