CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-105852

CVE-2026-105852: Authorization Bypass and Related-Document Oracle in Payload CMS

Amit Schendel
Amit Schendel
Senior Security Researcher

Oct 6, 2026·6 min read·14 visits

Executive Summary (TL;DR)

Unauthenticated attackers can bypass read-access controls on restricted collections via nested query parameters on related public collections, leaking metadata and confirming document existence.

An authorization bypass vulnerability in Payload CMS enables unauthenticated attackers to query and infer the existence of restricted documents via nested relationship queries on public collections. This cross-document contamination flaw affects both MongoDB and Drizzle SQL database adapters, allowing unauthorized reads of relationship metadata.

Vulnerability Overview

Payload CMS utilizes a collection-based data model where documents can establish relationships with documents in other collections using relationship, upload, or join fields. Access control in Payload CMS is applied at the collection level through authorization rules defined in the schema. When a user requests a collection, Payload CMS evaluates these rules and injects matching query constraints to restrict the returned dataset to only authorized documents.

This vulnerability arises from an authorization alignment misalignment when querying a publicly readable parent collection that contains relationships pointing to a restricted collection. Attackers can execute nested query parameters targeting fields within the restricted collection. Because the query parser evaluates the user's search criteria and the security restrictions independently, unauthenticated users can bypass the access.read policies of the related collection.

The flaw behaves as a related-document oracle or a cross-document contamination channel. While the attacker cannot directly fetch the full contents of the unauthorized documents, they can leverage the public endpoints to verify the existence of specific restricted documents, probe sensitive fields, and extract relationship metadata.

Root Cause Analysis

The root cause of this vulnerability lies in the independent resolution of user-supplied filters and system-enforced authorization policies across multi-document relationships. When an incoming query filters on a related document field, the query builder constructs the query differently depending on the active database adapter, but both adapters suffered from logical decoupling.

In the MongoDB adapter, queries targeting relationships (such as arrays of document IDs) were evaluated using implicit array matching. When a query is structured as { $and: [ { 'posts.title': 'archived' }, { 'posts.title': { $ne: 'archived' } } ] }, MongoDB satisfies this query if any element in the array matches the first condition, and any element (even a completely different one) matches the second condition. If a parent document links to one archived post and one public post, the query evaluates to true, leaking the relationship to the restricted archived document.

In the Drizzle SQL adapter, the query engine generated distinct table JOIN clauses for the user-supplied query and the injected authorization constraints. Because these constraints were evaluated on different alias variables representing distinct rows in the joined database table, the relational database matched parent records that had any association with an authorized row, regardless of whether the specific row matching the user's filter was authorized.

Code-Level Analysis and Patch Review

The vulnerability was mitigated in commit 94059cf4bc6170ce88453015c0c6551329ae3982 by rewriting the query compilers to evaluate user-supplied filters and access-control criteria against the exact same related document.

In the MongoDB adapter (packages/db-mongodb/src/queries/buildSearchParams.ts), the query parser now isolates relationship filters by executing a sub-query directly against the model of the related collection. This sub-query enforces access-control parameters within the target collection context first, then returns only the authorized IDs using the $in operator:

// Directly build the query on the related model (which automatically injects access control)
const matchingRelatedDocumentsQuery = await RelatedModel.buildQuery({
  locale: pathLocale ?? locale,
  payload,
  where: nestedWhere,
})
 
// Retrieve authorized and matching related document IDs only
const matchingRelatedDocumentIDs = (
  await RelatedModel.find(matchingRelatedDocumentsQuery).lean().select({ _id: true })
).map((document) => document._id)
 
// Enforce parent query to match using $in against ONLY verified/authorized IDs
return {
  path,
  value: { $in: matchingRelatedDocumentIDs },
}

In the Drizzle/SQL adapter (packages/drizzle/src/queries/parseParams.ts), the SQL query compiler was corrected to reuse the exact same join table alias variable. This forces SQL engines to apply both the user filter and the authorization rules within the same JOIN context rather than creating duplicate joins.

> [!WARNING] > Scale-Based Denial of Service (DoS) Risk: > In the MongoDB mitigation, the query engine retrieves all matching related document IDs into memory before passing them to the parent query via an $in clause. For collections containing millions of matching records, this execution path can result in substantial memory pressure, network latency, and potential application crashes if the retrieved document ID list exceeds memory bounds or MongoDB's BSON document limits.

Exploitation Methodology and Test Simulation

Exploitation of this vulnerability requires no authentication and can be completed through standard API query structures. Consider an application with a restricted posts collection and a public post-references collection containing a relationship field pointing to posts.

An administrator configures an authorization constraint on the posts collection to hide archived items from unauthenticated guests:

// posts read-access policy
read: ({ req }) => (req.user ? true : { title: { not_equals: 'archived' } })

An unauthenticated attacker sends an HTTP request querying the public collection, searching specifically for related records that are marked as 'archived'. The request is structured as follows:

GET /api/post-references?where[post.title][equals]=archived HTTP/1.1
Host: vulnerable-payload-cms.local
Accept: application/json

Before the patch, the application returns the parent post-reference document containing the reference ID of the restricted post, confirming that a post titled 'archived' exists. After applying the patch, the query returns an empty dataset because no single referenced post satisfies both conditions simultaneously (being titled 'archived' and not being titled 'archived').

Impact and Security Implications

The security impact of CVE-2026-105852 is classified as a medium-severity authorization bypass. Because the vulnerability targets relationship boundaries, an attacker cannot extract arbitrary database columns unless those columns are explicitly referenced within nested where queries.

However, this vulnerability constitutes a highly reliable side-channel oracle. Attackers can programmatically brute-force and deduce the values of restricted fields (e.g., verifying draft article titles, leaking user identifiers, or mapping out confidential relational links). This metadata leakage is critical in environments where the existence of a link itself is sensitive information, such as medical systems, private repositories, or multi-tenant database environments.

Furthermore, the severity escalates if combined with performance bugs or other logical flaws. The database adapter's structural limits could be triggered intentionally, allowing attackers to construct nested queries on large collections to degrade system performance.

Remediation and Mitigation Strategies

To fully remediate this vulnerability, organizations must upgrade all core Payload CMS packages and associated database adapters to version 3.90.0 or higher, or canary versions >= 4.0.0-canary.34.

Execute the dependency update using the appropriate package manager:

npm install payload@latest @payloadcms/db-mongodb@latest @payloadcms/db-postgres@latest

If immediate patching is not possible, implement the following defensive actions:

  1. Review collection configurations to identify any relationship, upload, or join fields that connect public collections to restricted target collections.
  2. Implement a custom validation middleware to intercept incoming HTTP requests and strip or reject nested query parameters that traverse restricted relationships.
  3. Implement field-level access control on relation fields within the public collections to restrict unauthenticated users from reading or querying those relationship definitions.

Official Patches

payloadcmsFix commit implementing relationship queries authorization fix.

Fix Analysis (1)

Technical Appendix

CVSS Score
5.3/ 10
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Affected Systems

Payload CMS (npm package: payload)

Affected Versions Detail

Product
Affected Versions
Fixed Version
payload
payloadcms
< 3.90.03.90.0
payload
payloadcms
>= 4.0.0-canary.0 < 4.0.0-canary.344.0.0-canary.34
AttributeDetail
CWE IDCWE-862 (Missing Authorization)
Attack VectorNetwork (AV:N)
CVSS v4.0 Score5.3 (Medium)
EPSS ScoreNot Available
ImpactInformation Disclosure / Related-Document Oracle
Exploit StatusProof of Concept (PoC) documented in integration test suite
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1068Exploitation for Privilege Escalation
Privilege Escalation
CWE-862
Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Vulnerability Timeline

Vulnerability published and advisory released by Payload CMS team
2026-10-06
Patches published in version 3.90.0 and 4.0.0-canary.34
2026-10-06

References & Sources

  • [1]Official GitHub Security Advisory
  • [2]Official Fix Commit Patch
  • [3]Payload v3.90.0 Release Notes
  • [4]CVE-2026-105852 National Vulnerability Database Entry

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•23 minutes ago•CVE-2026-122244
7.7

CVE-2026-122244: Stored Cross-Site Scripting in Budibase Builder Formula Evaluation

CVE-2026-122244 (GHSA-r2q3-7m4h-63qg) is a high-severity cross-privilege Stored Cross-Site Scripting (XSS) vulnerability in Budibase prior to version 3.50.0. The flaw occurs due to defective character escaping in the JSON formatter utility combined with raw HTML rendering via Svelte's {@html} directive in the Budibase Builder interface. A low-privileged application user or an unauthenticated form visitor can store malicious HTML markup in a shared datasource, which subsequently executes arbitrary JavaScript in the browser session of an administrator or application builder inspecting Handlebars formula bindings.

Amit Schendel
Amit Schendel
1 views•9 min read
•about 1 hour ago•CVE-2026-122247
8.2

CVE-2026-122247: Unauthenticated Global-Admin and Database Creation via Tenant-Confusion Bypass in Budibase

A tenant-confusion vulnerability in the user initialization endpoint of the Budibase worker service (prior to version 3.50.0) allows unauthenticated remote attackers to bypass the one-time administrative setup guard. By supplying arbitrary tenant identifiers in POST requests to /api/global/users/init, an attacker can force the underlying CouchDB datastore to dynamically provision unlimited tenant databases and persist latent global administrator accounts. This results in datastore resource exhaustion, denial of service, and unauthorized administrative account creation inside non-default tenant contexts.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 2 hours ago•CVE-2026-103026
8.1

CVE-2026-103026: Arbitrary Method Invocation and State Tampering in Paymenter via Livewire HasConfirmation Trait

Paymenter versions prior to 1.5.7 contain an arbitrary method invocation vulnerability within the base Livewire component architecture. The application includes a legacy trait, HasConfirmation, inside app/Livewire/Component.php, which is inherited across 36 client-facing Livewire components. This trait exposes a public remote procedure call (RPC) endpoint named executeConfirmedAction without access controls or method allowlisting. Remote attackers can invoke arbitrary methods on any inheriting component, including Livewire's internal fill() method, enabling them to bypass #[Locked] property protections and manipulate internal component state and hydrated Eloquent models.

Alon Barad
Alon Barad
2 views•9 min read
•about 3 hours ago•CVE-2026-104885
6.3

CVE-2026-104885: Cross-Realm MQTT Session Disconnect via Missing Authorization in OpenRemote

OpenRemote prior to version 1.31.0 contains a Missing Authorization vulnerability (CWE-862) in the user management REST API endpoint responsible for disconnecting active MQTT sessions. The disconnectUserSession method in UserResourceImpl fails to verify whether the requesting user owns the target MQTT session, holds administrative privileges, or belongs to the realm specified in the request path. As a result, any authenticated user who obtains a valid MQTT session identifier can forcefully terminate active MQTT connections belonging to other users or IoT devices across any tenant realm.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 4 hours ago•CVE-2026-69133
5.3

CVE-2026-69133: Cumulation Buffer Memory Retention in Netty OHTTP Codec

CVE-2026-69133 (GHSA-cg26-4c6j-2x8h) is a missing resource release vulnerability (CWE-772) in io.netty.incubator:netty-incubator-codec-ohttp affecting versions 0.0.20.Final through 0.0.26.Final. Both OHttpClientCodec and OHttpServerCodec retain the outer cumulationBuffer at its expanded high-water capacity after an Oblivious HTTP (OHTTP) exchange finishes. A remote unauthenticated attacker can complete a large OHTTP request or response over an HTTP keep-alive connection and leave the connection idle, pinning pooled or direct memory allocations across concurrent connections to induce denial of service.

Amit Schendel
Amit Schendel
2 views•8 min read
•about 5 hours ago•CVE-2026-104773
6.8

CVE-2026-104773: Session Fixation in CKAN User Registration View

A session fixation vulnerability (CWE-384) exists in CKAN (Comprehensive Knowledge Archive Network) prior to versions 2.10.11 and 2.11.6. When configured with server-side session storage and active public web registration, the user registration view programmatically authenticates newly created accounts without regenerating the active session identifier. An attacker capable of fixing or capturing a victim's pre-authentication session cookie can hijack the newly registered account immediately after registration completes.

Alon Barad
Alon Barad
3 views•9 min read