NocoDB has Prototype Pollution in Connection Test Endpoint, Leading to DoS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.9 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-24766: 0.42% estimated exploitation activity in the next 30 days; percentile 36.65 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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): The testConnection endpoint (packages/nocodb/src/controllers/utils.controller.ts) passes user-controlled input directly to deepMerge(): 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.

Published by the source

28 Jan 2026, 21:41 UTC

Last modified by the source

3 Feb 2026, 03:06 UTC

Source last checked

26 Oct 2026, 12:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-95ff-46g6-6gw9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-95ff-46g6-6gw9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24766

Advisory: NocoDB has Prototype Pollution in Connection Test Endpoint, Leading to DoS
IDs: CVE-2026-24766, GHSA-95ff-46g6-6gw9
Record: https://patchnext.com/advisories/cve-2026-24766 (revision 2, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nocodb 0.301.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected < 0.301.0; fixed in 0.301.0

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-95ff-46g6-6gw9 (OSV record GHSA-95ff-46g6-6gw9 lists affected ranges: npm nocodb >=0 <0.301.0 (fixed))
- Verified: https://github.com/advisories/GHSA-95ff-46g6-6gw9 (GitHub-reviewed advisory GHSA-95ff-46g6-6gw9 lists affected ranges: npm nocodb >=0 <0.301.0)

Commands are suggestions: review each one before running it.