Skip to main content
Menu
CVEs

CVE

NocoDB denial of service in MetaService metadata logging

NocoDB from 0.300.0 before 2026.04.4 is affected, when a request leaves a lookup condition undefined. Fixed in 2026.04.4.

CVE-2026-126267EUVD-2026-125254GHSA-GCXW-8Q43-JHJCGHSA-H9X3-2642-6JRQ

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.04.4
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. NocoDB versions from 0.300.0 before 2026.04.4 are affected. A request must leave a lookup condition undefined so the metadata query log line fails to compile.

Published
Last modified
Reference
Last checked
0.35% · 29th percentile
15/100
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

NocoDB from 0.300.0 before 2026.04.4 contains a denial of service vulnerability that allows authenticated users to crash the server by triggering an unhandled promise rejection in MetaService metadata logging. Attackers can send a request leaving a lookup condition undefined, causing knex binding errors in the unawaited logHelper call that terminate the server process.

Who should check

Teams running self-hosted or deployed NocoDB from 0.300.0 before 2026.04.4 that allow authenticated users to make metadata requests.

“Affected versions >= 0.300.0, < 2026.04.4”

github.com

cve.now Index

15cve.now Index 15 of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    NocoDB versions from 0.300.0 before 2026.04.4 are affected. A request must leave a lookup condition undefined so the metadata query log line fails to compile.
  • Upgrade to a fixed version: 2026.04.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126267 (NocoDB from 0.300.0 before 2026.04.4 Denial of Service via MetaService Logging), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126267 (entry last updated 2026-11-13):
Affected:
- nocodb nocodb: from 0.300.0, fixed in 2026.04.4
Fixed versions: 2026.04.4.
Conditions (all must be true for the bug to be hit):
- NocoDB versions from 0.300.0 before 2026.04.4 are affected. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-gcxw-8q43-jhjc)
- A request must leave a lookup condition undefined so the metadata query log line fails to compile. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-gcxw-8q43-jhjc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126267 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126267 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-gcxw-8q43-jhjc
- https://www.vulncheck.com/advisories/nocodb-from-0.300.0-before-2026.04.4-denial-of-service-via-metaservice-logging
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126267
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126267"}.

Public exploit activity

100%0Nov 13Nov 17
  • EPSS: 0.35%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • nocodb nocodb

    From 0.300.0 · fixed in 2026.04.4

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126267

Is CVE-2026-126267 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An authenticated user can crash the whole NocoDB server process with a single request. The server stays down until a supervisor or an operator restarts it.Source: github.com

Which versions are affected by CVE-2026-126267?

nocodb: from 0.300.0 before 2026.04.4.Source: cve.now feed data

Am I affected, and how do I check?

NocoDB versions from 0.300.0 before 2026.04.4 are affected. The crash happens when a request leaves a lookup condition undefined, so the metadata query log line fails to compile. Compare your installed NocoDB version against that range to check.Source: github.com

How do I fix CVE-2026-126267?

Upgrade NocoDB to 2026.04.4 or later, which is the fixed version.Source: github.com