/

CVE-2026-85619

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-863) in AppFlowy Cloud Data

CVE-2026-85619

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-863

Impact:

Cross-Workspace Data Exposure and Modification

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

AppFlowy-Cloud contains an authorization flaw that does not properly verify whether requested collaboration objects belong to the requesting workspace. An attacker who can submit a victim's object identifier with their own workspace identifier may read, modify, or delete data across workspace boundaries.

Affected context

The vulnerability occurs in AppFlowy-Cloud deployments where authorization checks accept workspace and collaboration-object identifiers from a request without confirming that both identifiers refer to the same workspace. It may affect document and database-row operations when object ownership is not independently verified by the server.

Exploit preconditions

  • Attack surface: Authenticated application or API endpoints that operate on

collaboration objects

  • Required access: A valid account or session capable of issuing requests to

the affected operations

  • Trigger point: A request containing an object identifier and a workspace

identifier

  • Why exploitation is possible: Authorization logic trusts the supplied

workspace context without enforcing object-to-workspace ownership

Why this happens

The underlying bug is an incomplete authorization check. The application evaluates access using a caller-controlled workspace identifier but does not reliably confirm that the requested document or database row belongs to that workspace. This represents CWE-863, Incorrect Authorization, because the system permits an operation without fully validating the resource's actual ownership and access relationship.

Potential impact

  • Attackers may read documents or database rows from other workspaces
  • Attackers could modify cross-workspace content
  • Attackers could delete data belonging to other tenants
  • Confidential information may be exposed across workspace boundaries
  • Data integrity and tenant isolation may be weakened

General mitigation guidance

Mitigation generally focuses on enforcing server-side, object-level authorization for every operation. Secure-by-default designs should derive workspace context from trusted session or membership data and verify the requested object's ownership through a trusted datastore relationship rather than relying on request parameters. Authorization checks should cover read, update, and delete paths consistently, use least-privilege service identities, and fail closed when ownership cannot be established. Input validation can reduce malformed requests, but should not replace resource authorization.

How teams detect issues like this

Detection approaches may include static and semantic analysis for handlers that authorize resources using caller-supplied tenant or workspace identifiers, code review for missing object-to-tenant relationship checks, and policy enforcement requiring object-level authorization on every CRUD endpoint. Integration tests can verify that objects from one workspace cannot be accessed through another workspace context. Audit logging and monitoring can identify unusual cross-workspace object access patterns. Automated review tools may help flag inconsistent authorization paths.

Sources

SourceLink
github.comgithub.com/AppFlowy-IO/AppFlowy-Cloud
github.comgithub.com/AppFlowy-IO/AppFlowy-Cloud/blob/0.9.64/libs/access-control/src/casbin/collab.rs
github.comgithub.com/AppFlowy-IO/AppFlowy-Cloud/issues/1624
vulncheck.comvulncheck.com/advisories/appflowy-cloud-0.9.64-cross-workspace-collab-access-via-http-api

Frequently asked

questions

It may be exploitable through the affected application or API endpoints when

an attacker can submit authenticated requests containing object and

workspace identifiers.

Typically, some valid account or session access is required. The critical

issue is that ordinary workspace access may not be correctly restricted to

the requested object's actual workspace.

Perform server-side object-level authorization for every operation and verify

the resource's workspace association using trusted application state rather

than request-supplied context.

Use centralized authorization checks, enforce tenant isolation consistently,

test cross-tenant access cases, and monitor audit logs for unexpected

workspace-boundary violations.

Find out what's already
exploitable in your codebase.