# CVE-2026-116121: NocoDB Registration users.service.ts race condition


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-qw65-38gx-3749

## What is CVE-2026-116121?

CVE-2026-116121 is a medium-severity vulnerability in NocoDB, published on 26 Oct 2026. 

### Official description

A vulnerability was identified in NocoDB up to 2026.08.0. This issue affects some unknown processing of the file users.service.ts of the component Registration. Such manipulation leads to race condition. The attack may be performed from remote. The attack requires a high level of complexity. The exploitability is assessed as difficult. The vendor deleted the GitHub issue for this vulnerability without any explanation. Afterwards the vendor was contacted early about this disclosure via email but did not respond in any way.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-116121?


## How do I fix CVE-2026-116121?

No fix has been published for CVE-2026-116121 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116121 being exploited?

There is no known exploitation of CVE-2026-116121 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116121 and fix it if it is affected.

What it is: CVE-2026-116121 is a medium-severity vulnerability in NocoDB, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116121 in the wild and no public exploit code.

Affected product: NocoDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116121/ (Markdown: https://insights.sbomify.com/CVE-2026-116121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116121
- OSV: https://osv.dev/vulnerability/CVE-2026-116121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116121/
Summaries are generated and may contain mistakes; the official description above is the record.