CVE-2026-126273 is a NocoDB privilege escalation flaw during initial administrator setup. On a fresh, non-cloud instance, an administrator email paired with an empty administrator password silently skips the environment-based super-admin bootstrap.The first unauthenticated person to register can then receive organisation Creator and Super Admin roles. The NocoDB advisory rates the issue High; the CVE record assigns CVSS 4.0 9.2 Critical and CVSS 3.1 8.1 High.
What it allows
How Does CVE-2026-126273 Grant Admin Roles?
NocoDB says its environment-based bootstrap required both the administrator email and password to contain values. An empty password made the bootstrap skip the administrator account without an error or warning.
On a fresh non-cloud instance, NocoDB assigns the first registered user organisation Creator and Super Admin roles. If bootstrap created no account, the first unauthenticated registrant could take that position and gain full administrative control.
This is an initial-setup window before any user row exists. The advisory explicitly says the flaw does not bypass an administrator account that bootstrap successfully created. See the privilege escalation glossary for the role distinction.
What Does the Evidence Say About Exploitation?
The vendor advisory and CVE record describe the attack path, but neither documents an incident. CVE-2026-126273 was absent from the CISA KEV catalog version dated November 13, 2026.
On November 14, 2026, Brandefense's GitHub repository name search returned one public repository naming this CVE. That measures matching repositories, not working exploits or attacks.
How Should Teams Prioritize CVE-2026-126273?
Prioritize fresh NocoDB instances that were reachable before their first account was created, especially where the administrator password was left empty. A successfully created administrator account falls outside the advisory's stated exposure window.
Brandefense Blackhole counted two dark chat posts mentioning this CVE from August 16 through November 14, 2026. These are post mentions, not confirmed exploitation or incidents.
Use a vulnerability intelligence platform workflow to record the version, bootstrap configuration, first-account status, and follow-up. Treat the configuration and account review as separate checks from public signal monitoring.
Who is affected
Which NocoDB Installations Are Affected?
NocoDB lists versions earlier than 2026.09.0 as affected and 2026.09.0 as patched. The vulnerable condition requires a configured administrator email with an empty administrator password during initial bootstrap on a fresh, non-cloud instance.
Exposure lasts only until the first user account exists. Inspect the running NocoDB version and deployment configuration, then establish whether bootstrap created the intended administrator before public registration became reachable.
How Can Administrators Verify the Fix?
Upgrade affected deployments to NocoDB 2026.09.0 or later. After updating, check the running application version and confirm that the intended administrator account exists with the expected role.
Review the identity and creation time of the first user on installations that started with an empty administrator password. If the first account is unexpected, follow your incident response process and review its administrative actions.
Record the version check and account review in your patch management process. The vendor's version range uses a custom scheme, so this profile does not offer an automated comparison command.
Timeline
- 2026-10-27
NocoDB published GHSA-mjxv-r6j7-m8gv and identified 2026.09.0 as the patched version.
- 2026-11-13
The CVE Program published CVE-2026-126273 with CVSS 4.0 and 3.1 scores.
- 2026-11-14
Brandefense reviewed the vendor advisory, CVE record, CISA KEV lookup, and internal signal counts.
What to do
-
Find exposed fresh deployments
Inventory NocoDB installations earlier than 2026.09.0. Check which fresh non-cloud instances had an administrator email set while the administrator password was empty.
-
Update NocoDB
Upgrade affected installations to NocoDB 2026.09.0 or later. Verify the version reported by the running application after the update.
-
Validate the first administrator
Confirm the intended administrator account exists and holds the expected role. Review the first user's identity and creation time where bootstrap may have been skipped.
-
Investigate unexpected accounts
If an unexpected user became the first administrator, review that account's actions and follow your incident response process.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-126273 in Brandefense Atlas
The Atlas record of CVE-2026-126273: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can CVE-2026-126273 bypass an existing NocoDB administrator?
No. NocoDB limits this flaw to the initial setup window before any user row exists. It does not bypass an administrator account that was successfully created.
Which NocoDB version fixes CVE-2026-126273?
NocoDB lists 2026.09.0 as the patched version. Update earlier installations and verify the running version after deployment.
What configuration creates the exposure?
The administrator email is configured, but the administrator password is empty. On a fresh non-cloud instance, the skipped bootstrap can leave first-user registration open.
Is active exploitation confirmed for this CVE?
The opened NocoDB advisory and CVE record do not document an incident. The CVE was absent from CISA KEV catalog version 2026.11.13.
Sources
- Privilege Escalation via Incomplete Admin BootstrapNocoDB
- CVE-2026-126273 recordVulnCheck CNA via CVE Program
- Known Exploited Vulnerabilities CatalogCISA