CVE-2026-59262: Missing Authorization in affine monorepo
AFFiNE's histories GraphQL field fails to validate Doc.Read permission before exposing document edit history, allowing authenticated workspace members to retrieve restricted content timelines. Attackers can supply arbitrary document GUIDs to access full edit histories including user names, emails, and timestamps of private pages they lack access to.
AI Analysis
Technical Summary
The vulnerability in AFFiNE's monorepo arises from missing authorization checks on the histories GraphQL field. Specifically, the system fails to verify that a user has Doc.Read permission before returning the edit history of documents. As a result, any authenticated member of a workspace can supply arbitrary document GUIDs to retrieve complete edit histories, including sensitive metadata such as user names, emails, and timestamps, even for private documents they are unauthorized to view. This represents an information disclosure vulnerability with a CVSS 4.0 base score of 7.1 (high severity). No vendor advisory or patch information is currently available, and the product is not a cloud service, so remediation depends on vendor action or user mitigation.
Potential Impact
Authenticated workspace members can retrieve sensitive edit history information for documents they do not have permission to access. This includes user identities (names and emails) and timestamps related to document edits on private pages. The exposure of this information can lead to privacy violations and potential further targeted attacks based on disclosed user data. There is no indication of privilege escalation or remote code execution, but the confidentiality of restricted content timelines is compromised.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or temporary workaround is currently documented, organizations should restrict workspace membership to trusted users and monitor access to sensitive documents. Avoid sharing document GUIDs publicly and consider limiting GraphQL API access where feasible until a patch is released.
CVE-2026-59262: Missing Authorization in affine monorepo
Description
AFFiNE's histories GraphQL field fails to validate Doc.Read permission before exposing document edit history, allowing authenticated workspace members to retrieve restricted content timelines. Attackers can supply arbitrary document GUIDs to access full edit histories including user names, emails, and timestamps of private pages they lack access to.
CVSS v4.0
Score 7.1high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in AFFiNE's monorepo arises from missing authorization checks on the histories GraphQL field. Specifically, the system fails to verify that a user has Doc.Read permission before returning the edit history of documents. As a result, any authenticated member of a workspace can supply arbitrary document GUIDs to retrieve complete edit histories, including sensitive metadata such as user names, emails, and timestamps, even for private documents they are unauthorized to view. This represents an information disclosure vulnerability with a CVSS 4.0 base score of 7.1 (high severity). No vendor advisory or patch information is currently available, and the product is not a cloud service, so remediation depends on vendor action or user mitigation.
Potential Impact
Authenticated workspace members can retrieve sensitive edit history information for documents they do not have permission to access. This includes user identities (names and emails) and timestamps related to document edits on private pages. The exposure of this information can lead to privacy violations and potential further targeted attacks based on disclosed user data. There is no indication of privilege escalation or remote code execution, but the confidentiality of restricted content timelines is compromised.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or temporary workaround is currently documented, organizations should restrict workspace membership to trusted users and monitor access to sensitive documents. Avoid sharing document GUIDs publicly and consider limiting GraphQL API access where feasible until a patch is released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-04T12:17:14.302Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4e73c0c9d9e3dbe3604295
Added to database: 07/08/2026, 15:58:56 UTC
Last enriched: 07/08/2026, 16:13:49 UTC
Last updated: 07/09/2026, 01:25:36 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.