CVE-2026-24766: NocoDB Vulnerable to Prototype Pollution in Connection Test Endpoint, Leading to DoS

Published Jan 28, 2026
·
Updated

Summary

An authenticated user with org-level-creator permissions can exploit prototype pollution in the /api/v2/meta/connection/test endpoint, causing all database write operations to fail application-wide until server restart.

While the pollution technically bypasses SUPERADMIN authorization checks, no practical privileged actions can be performed because database operations fail immediately after pollution.

Details

The deepMerge() function in packages/nocodb/src/utils/dataUtils.ts does not sanitize the following keys: (proto, constructor, prototype):

typescript export const deepMerge = (target: any, ...sources: any[]) => { // ... Object.keys(source).forEach((key) => { if (isMergeableObject(source[key])) { if (!target[key]) target[key] = Array.isArray(source[key]) ? [] : {}; deepMerge(target[key], source[key]); // Recursively merges proto } else { target[key] = source[key]; } }); // ... };

The testConnection endpoint (packages/nocodb/src/controllers/utils.controller.ts) passes user-controlled input directly to deepMerge():

typescript config = await integration.getConfig(); deepMerge(config, body);

When an attacker sends {"proto": {"super": true}}, the super property is written to Object.prototype, affecting all plain objects in the Node.js process.

Impact

Pollutes Object.prototype globally, breaking all subsequent database write operations for all users until process restart.

Other sources

NocoDB is software for building databases as spreadsheets. Prior to version 0.301.0, an authenticated user with org-level-creator permissions can exploit prototype pollution in the /api/v2/meta/connection/test endpoint, causing all database write operations to fail application-wide until server restart. While the pollution technically bypasses SUPERADMIN authorization checks, no practical privileged actions can be performed because database operations fail immediately after pollution. Version 0.301.0 patches the issue.

— MITRE

Affected Software

3 affected componentsFixes available
npm/nocodb<0.301.0
npm/nocodb<0.301.0
0.301.0
NocoDB NocoDB<0.301.0

Event History

Jan 28, 2026
CVE Published
via MITRE·08:27 PM
Data Sourced
via MITRE·08:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:41 PM
Data Sourced
via GitHub·09:41 PM
DescriptionSeverityWeaknessAffected Software
Jul 24, 58068
Event
via FIRST·05:24 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-24766?

CVE-2026-24766 is classified as a medium severity vulnerability due to its potential to cause denial of service.

2

How do I fix CVE-2026-24766?

To fix CVE-2026-24766, update NocoDB to version 0.301.0 or later.

3

Who is affected by CVE-2026-24766?

CVE-2026-24766 affects authenticated users with org-level-creator permissions in versions of NocoDB prior to 0.301.0.

4

What type of attack does CVE-2026-24766 enable?

CVE-2026-24766 enables prototype pollution attacks, which can lead to application-wide failures in database operations.

5

Is there a workaround for CVE-2026-24766?

There are no known workarounds for CVE-2026-24766; the recommended approach is to upgrade to the fixed version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203