On this page (7 sections)
A critical SQL injection flaw, tracked as CVE-2026-130706, affects NocoDB versions before 2026.09.0. According to the GitHub Advisory Database entry, a logged-in user with the Creator or Owner role can inject raw SQL through a crafted formula, and the result can be escalation to super administrator or, on external PostgreSQL hosts, execution of operating system commands.
If you self-host NocoDB, especially with an external PostgreSQL database, or you give Creator access to people you do not fully trust, you should check your version now. Details are still limited, and this article marks clearly what is and is not confirmed.
What happened
The CVE was published on November 18, 2026 and describes an SQL injection in NocoDB. The description says an authenticated user with the Creator or Owner role can inject raw SQL by persisting a crafted formula whose stored parsed tree is later reused without being validated again. In plain terms, the application checks the formula once, saves a processed form of it, and then trusts that saved form when building database queries.
The same description says an attacker can bypass the guard that protects the SQLite metadata path by using an alias to plant that tree. The stated outcomes are escalation to super administrator, or executing OS commands on external PostgreSQL hosts.
Technical details
The weakness class is CWE-89, improper neutralization of special elements in SQL commands. SQL injection happens when user-controlled input ends up inside a database query as code instead of as data. Here, the input is a formula, a feature that lets users define computed fields. The flaw described resembles a time-of-check versus time-of-use gap: the formula's stored tree is reused later without being revalidated.
The advisory's CVSS v4 metrics list a network attack vector, low attack complexity, no attack requirements, no user interaction, and high privileges required. Confidentiality, integrity and availability impact are all rated high, for both the vulnerable system and subsequent systems. The high privileges requirement matches the description: the attacker must already hold a Creator or Owner account.
That prerequisite lowers the risk for installs where only a few trusted people hold those roles, but it does not remove it. Stolen or reused credentials, a compromised team member's account, or an overly generous role assignment would all satisfy it. The impact on external PostgreSQL hosts is the most serious part, because OS command execution there reaches beyond NocoDB itself.
Who is affected
- Self-hosted NocoDB installations running a version earlier than 2026.09.0.
- Installations that connect to an external PostgreSQL server, where the description says OS command execution is possible.
- Teams that grant the Creator or Owner role widely, to contractors, shared accounts or users outside the core team.
- Instances reachable from the internet, since the attack vector is rated Network.
The research does not say whether NocoDB's hosted cloud service is affected or already updated, and it does not describe any vendor fix notes. If you use a hosted service, ask the provider or check NocoDB's official communications.
How to check your exposure
First find out which version you run. Your NocoDB interface or deployment configuration should show it, which is the quickest read-only check. If you run NocoDB in Docker, this standard command lists local images and tags so you can see which one your host uses. Run it on the Docker host and look for the NocoDB image tag.
docker images | grep -i nocodbIf you installed another way, use that tool's own version or list command instead. Any version older than 2026.09.0 should be treated as vulnerable. Then review who holds elevated roles:
- List every user with the Creator or Owner role in each workspace and base.
- Remove or downgrade accounts that no longer need that access.
- Look for unfamiliar formula fields, or formulas edited recently by accounts that rarely change schema.
- Check whether any unexpected super administrator accounts have appeared.
What to do now
- Confirm your NocoDB version and upgrade to 2026.09.0 or later, following NocoDB's official upgrade instructions.
- Take a backup of your NocoDB metadata database and data sources before upgrading.
- Until you can upgrade, restrict Creator and Owner roles to the smallest set of trusted users.
- Rotate passwords and API tokens for Creator and Owner accounts, and enable stronger authentication if available.
- Do not expose NocoDB directly to the internet if it is not needed; place it behind a VPN or an IP allowlist.
- Review the database account NocoDB uses for external PostgreSQL and remove superuser or other privileges it does not need.
- Review recent formula changes and administrator accounts for anything you cannot explain.
Detection and monitoring
The research gives no indicators of compromise, so detection has to be general. Watch PostgreSQL logs for unusual statements coming from the NocoDB database user, such as queries touching system catalogs or administrative functions. Review any available NocoDB activity logs for formula creation and edits. Alert on new super administrator accounts and on role changes.
On the network side, keep an eye on unexpected outbound connections from the NocoDB host and from your PostgreSQL server, since command execution would often lead to that. If you suspect abuse, follow the steps in Website hacked: what to do and rotate every credential stored in your connected data sources.
For internet-facing instances, Webforta Monitor can track uptime, certificate and DNS changes on the domain that serves your NocoDB, which helps you notice unplanned changes. It does not detect or block this specific flaw, so version updates and role hygiene remain the main defense.
What is still unknown
- Whether the flaw is being exploited. The research reports no exploitation, and the CVE is not listed in CISA KEV.
- The exact patched version. The advisory's fields say Unknown, while the description says before 2026.09.0.
- Whether a workaround exists other than limiting roles and upgrading.
- Full technical detail, since only one advisory text is available and it is marked Unreviewed.
Check the GitHub advisory, the NVD record and the NocoDB repository's linked advisory GHSA-frqc-xh5h-rrcw for updates. For more security news and analysis, browse the Webforta blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
