CVE-2026-126282 in NocoDB
Summary
by MITRE • 11/13/2026
NocoDB from 2026.04.0 before 2026.08.0 contains an improper privilege management vulnerability in org-users.service.ts where updating a user's legacy organization role rewrites their default-workspace role. Revoked users can silently regain Creator-level read, write and schema modification access across all default-workspace bases using their existing session token.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/13/2026
The identified vulnerability resides within the NocoDB application, specifically in the org-users.service.ts module which handles user organization management logic between versions 2026.04.0 and 2026.08.0. This flaw represents a critical failure in access control mechanisms where the system incorrectly manages privilege transitions during role updates. The core technical issue is an improper privilege assignment that occurs when an administrator attempts to update a user's legacy organization-level role. Instead of isolating or correctly mapping these permissions, the underlying code logic inadvertently triggers a rewrite of the user's default-workspace roles. This behavior creates a dangerous side effect where permission states are not updated in isolation but rather cascade incorrectly across different scopes of access control within the application architecture.
The operational impact of this vulnerability is severe because it allows for privilege escalation without requiring authentication bypass or credential theft. An attacker who has been revoked from an organization, meaning their active sessions should theoretically be invalidated or restricted to minimal read-only access depending on policy, can exploit this logic error by triggering a role update operation. By doing so, the system silently restores Creator-level permissions within the default workspace. This restoration includes full read and write capabilities as well as schema modification rights across all bases associated with that default workspace. Consequently, previously revoked users regain comprehensive control over sensitive data structures and content, effectively nullifying security revocation actions taken by administrators.
From a classification perspective, this vulnerability aligns closely with CWE-269 Improper Privilege Management, specifically illustrating how incorrect handling of role assignments leads to unauthorized elevation of privileges. The attack vector leverages the application's own administrative functions against itself, which is characteristic of logic flaws often categorized under ATT&CK technique T1078 Valid Accounts when combined with privilege escalation tactics like T1068 Exploitation for Privilege Escalation. Although the attacker uses a valid session token that was previously active, the exploitation relies on manipulating state transitions rather than breaking cryptographic protections or exploiting buffer overflows. This makes detection through standard intrusion prevention systems difficult as the traffic appears to be legitimate administrative activity from an authorized user identity until the privilege change occurs.
Mitigation strategies must focus on immediate patching and rigorous validation of role update operations. Administrators should upgrade NocoDB to version 2026.08.0 or later where this logic error has been corrected in the source code. In environments where upgrading is not immediately feasible, a temporary workaround involves implementing strict monitoring for any changes to default-workspace roles following organization-level updates. Security teams should audit logs for unexpected privilege escalations and ensure that revocation processes include explicit invalidation of all associated session tokens rather than relying solely on role status flags. Additionally, developers must review the org-users.service.ts implementation to enforce separation of concerns between organizational permissions and workspace-specific permissions, ensuring that changes at one level do not inadvertently alter access controls at another unrelated or subordinate level without explicit intent and validation.