Skip to main content
Menu
CVEs

CVE

NocoDB information disclosure via SQL injection in column defaults

Affects NocoDB before 2026.08.0 with column default values on PostgreSQL or MySQL bases, where the user has schema-edit permission (Creator or Owner role). Fixed in 2026.08.0.

CVE-2026-130715Published Updated Summary written by a model

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

Do first: Check whether your setup matches what the bug needs. Column default values set on PostgreSQL or MySQL bases Attacker needs schema-edit permission on the base (Creator or Owner role)

Summary

NocoDB before 2026.08.0 contains an sql injection vulnerability that allows authenticated Creator or Owner users to execute database functions by supplying zero-argument function calls as column default values. Attackers can plant functions like version() or inet_server_addr() in PostgreSQL or MySQL column definitions and read results through record APIs, disclosing server addresses, role names, and engine details.

Who should check

Teams running NocoDB before 2026.08.0 on PostgreSQL or MySQL bases where Creator or Owner users can edit columns.

“Exploitation requires an authenticated account with schema-edit permission on the base, that is the Creator or Owner base role”

github.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • 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.

    Column default values set on PostgreSQL or MySQL bases Attacker needs schema-edit permission on the base (Creator or Owner role)
  • Upgrade to a fixed version: 2026.08.0.

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-130715 (NocoDB before 2026.08.0 SQL Injection via Zero-Argument Functions in Column Defaults), 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-130715 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.08.0
Fixed versions: 2026.08.0.
Conditions (all must be true for the bug to be hit):
- Column default values set on PostgreSQL or MySQL bases (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4w2w-wj9x-f4fv)
- Attacker needs schema-edit permission on the base (Creator or Owner role) (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4w2w-wj9x-f4fv)
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-130715 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130715 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-4w2w-wj9x-f4fv
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-130715
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-130715"}.

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

    fixed in 2026.08.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-4w2w-wj9x-f4fv
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130715
RecordNVD · CVE-2026-130715

Corrections

None so far.

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

Questions about CVE-2026-130715

Is CVE-2026-130715 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?

Column default values that match a zero-argument database function shape are written verbatim into the generated column definition, which allows SQL injection. The injected function results are returned through normal record reads, disclosing details such as engine version, database and role names, server addresses, and replica state.Source: github.com

Which versions are affected by CVE-2026-130715?

nocodb: before 2026.08.0.Source: cve.now feed data

Am I affected, and how do I check?

NocoDB versions before 2026.08.0 are affected where column default values are set on PostgreSQL or MySQL bases, and the account has schema-edit permission on the base (Creator or Owner role). To check, look at the NocoDB version in your deployment or image tag, and check whether any PostgreSQL or MySQL base uses column default values.Source: github.com

How do I fix CVE-2026-130715?

Upgrade NocoDB to 2026.08.0 or later.Source: github.com

More CVEs