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-105853

CVE-2026-105853: Sensitive Information Disclosure and Authentication Collection Boundary Bypass in Payload CMS

Amit Schendel
Amit Schendel
Senior Security Researcher

Oct 6, 2026·5 min read·59 visits

Executive Summary (TL;DR)

Payload CMS fails to sanitize user documents in password reset and token refresh endpoints, allowing low-privileged authenticated users to access hidden or read-restricted fields across collection boundaries.

CVE-2026-105853 is a high-severity information disclosure vulnerability in Payload CMS that affects authentication-enabled collections. In vulnerable versions, the application fails to properly serialize and sanitize user documents during token refresh and password reset operations. This deficiency leaks hidden and read-restricted fields to unauthorized actors. Additionally, a logical flaw in token refresh validation allows low-privileged users to cross collection boundaries, exposing sensitive configuration details and administrative metadata.

Vulnerability Overview

Payload CMS is an open-source headless content management system built on Node.js. It features authentication-enabled collections, allowing developers to manage different classes of users (such as public users and administrators) with fine-grained access control policies. Each collection has its own schema where developers can define security attributes, including fields hidden from API responses (hidden: true) or fields restricted by custom read-access controls.

In affected versions, the endpoints responsible for processing token refresh and password reset operations contain integration flaws. They bypass the standard field-level serialization and sanitization pipelines. This omission exposes the raw user document directly to the client, undermining the security guarantees defined in the application schema.

Furthermore, the system fails to validate authorization boundaries between separate authentication collections during token refresh operations. This allows an authenticated user from a low-privilege collection to query the refresh endpoint of a high-privilege collection. The vulnerability represents a serious risk of internal privilege escalation and data harvesting in multi-tenant or multi-collection installations.

Root Cause Analysis

The underlying security issue is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). It stems from two distinct logical errors in the authentication controllers.

First, standard Payload CMS operations run user documents through a sanitization pipeline before returning them to the client. This pipeline checks permissions and strips any fields flagged as hidden or fields that the requester does not have read-access to. However, the token refresh and password reset controllers directly retrieved user objects from the database and serialized them straight into the JSON response. This omission allowed any requester capable of triggering these endpoints to inspect internal system fields, custom roles, password reset tokens, and API keys.

Second, the token refresh operation did not enforce boundaries between different authenticated collections. When an authenticated client invokes the refresh endpoint, the application decodes the JSON Web Token (JWT) and validates the session. However, the system failed to verify whether the collection associated with the active token (req.user.collection) matched the target collection route being called (collectionConfig.slug). Consequently, a low-privilege user could submit their token to a high-privilege refresh route, bypassing namespace isolation and forcing the server to return the non-sanitized user document.

Code-Level Analysis

The fix for the collection-boundary validation bypass was introduced in commit f5f1283d275c58b30e2faa6be7cdc4d49451ea91 inside the file packages/payload/src/auth/operations/refresh.ts.

Prior to the patch, the refreshOperation handler validated the presence of the authenticated user in the request context but did not verify the collection source:

// Before Patch
if (!args.req.user) {
  throw new Forbidden(args.req.t)
}

The patch introduced strict checking of the user's collection against the collection configuration of the active route:

// After Patch
import { status as httpStatus } from 'http-status'
import { APIError, Forbidden } from '../../errors/index.js'
 
// ... within refreshOperation ...
if (!args.req.user) {
  throw new Forbidden(args.req.t)
}
if (args.req.user.collection !== collectionConfig.slug) {
  throw new APIError('Incorrect collection', httpStatus.FORBIDDEN)
}

This addition ensures that if the authenticated user's collection identifier does not match the target collection slug, an explicit 403 Forbidden APIError is raised immediately. To mitigate the broader field-leakage issue, additional sanitization wrappers were added to the endpoint outputs, ensuring that all returned objects are filtered using the standard schema access-control rules.

Attack Methodology

An attacker can exploit this vulnerability through two separate vectors, depending on their level of access. In the first vector, the attacker exploits the cross-collection boundary to obtain hidden metadata. The workflow is demonstrated in the sequence diagram below:

In the second vector, an attacker triggers the password reset flow using the /api/users/forgot-password and /api/users/reset-password endpoints. When the reset is completed, the server returns the updated user document to the client. Because the handler lacks serialization, the response includes fields that are explicitly designated as hidden, such as internal access levels or secret keys.

Security Impact Assessment

The impact of this vulnerability is significant for multi-tenant and multi-role configurations. The disclosure of hidden fields allows attackers to read internal access control attributes, backend flags, and reference IDs that are crucial for application logic.

While the vulnerability does not directly allow remote code execution or unauthorized database modification, the leaked metadata often contains the information necessary to construct subsequent high-impact attacks. For example, exposing internal user roles or secret configuration variables can allow an attacker to identify flaws in custom access control hooks.

According to the CVSS v4.0 calculator, the base score is 7.1 (High) with the vector string CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N. This calculation indicates that the network-accessible, low-complexity exploit has high confidentiality impact on the target system.

Remediation and Mitigation Guidance

The primary recommendation is to update the application dependencies to a secure version. The vendor has released patches that address both the collection validation logical flaw and the field-level leakage.

Users operating on the 3.x release branch must upgrade the core payload package to version 3.90.0 or higher. Users on the 4.x development or canary branches must upgrade to version 4.0.0-canary.34 or higher.

Additionally, developers utilizing custom authentication strategies must review their implementations. The vendor advisory notes that custom authentication strategies remain responsible for filtering user documents returned through custom responses. Developers must ensure that all custom login, token-refresh, or identity-validation endpoints manually run user records through the standard Payload sanitization utilities prior to transmitting payload structures.

Official Patches

Payload CMSOfficial Security Advisory
Payload CMSPrimary Fix Commit
Payload CMSVersion 3.90.0 Release Tag

Fix Analysis (1)

Technical Appendix

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

Affected Systems

Payload CMS installations with multiple authentication-enabled collectionsPayload CMS installations with custom fields marked as hidden

Affected Versions Detail

Product
Affected Versions
Fixed Version
payload
Payload CMS
>= 3.0.0, < 3.90.03.90.0
payload
Payload CMS
>= 4.0.0-canary.0, < 4.0.0-canary.344.0.0-canary.34
AttributeDetail
CWE IDCWE-200
Attack VectorNetwork (AV:N)
CVSS v4.0 Score7.1
EPSS ScoreNot yet populated
ImpactHigh Confidentiality Exposure
Exploit Statuspoc
KEV StatusNo

MITRE ATT&CK Mapping

T1552Unsecured Credentials
Credential Access
T1005Data from Local System
Collection
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor who is not authorized to have access to that information.

Vulnerability Timeline

Fix commit pushed to Payload core repository
2026-09-02
CVE Published on NVD and GitHub Advisory Database
2026-10-06

References & Sources

  • [1]GitHub Security Advisory GHSA-xgv3-crq2-6f69
  • [2]Fix Commit (Token Refresh Collection Boundary)
  • [3]Payload CMS Release Version 3.90.0

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