---
id: "CVE-2026-126280"
page: "https://infrastack.ai/live/CVE-2026-126280"
kind: "vulnerability"
aliases: ["CVE-2026-126280"]
title: "NocoDB: refresh-token race lets captured tokens mint sessions"
severity: "critical"
cvss: 9.1
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "nocodb", "fixed": [], "affected": "", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["auth", "nocodb", "package", "self-hosted"]
not_affected_if: ["version-2026.08.0-or-later"]
published_at: "2026-11-13T10:17:31+00:00"
first_seen_at: "2026-11-13T10:47:13+00:00"
updated_at: "2026-11-13T10:48:41+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126280", "first_seen_at": "2026-11-13T10:47:13+00:00"}]
exploit_sources: []
---

# NocoDB: refresh-token race lets captured tokens mint sessions

Link for people: https://infrastack.ai/live/CVE-2026-126280 (this .md is for agents)

NocoDB before 2026.08.0 has a race condition in refresh-token rotation, because the code never checks how many rows an update touched. An attacker holding a captured refresh token can present it concurrently with the legitimate user and obtain a valid authenticated session, with no reuse event recorded.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:nocodb affected range not listed fixed no fixed version listed

## How to check

- Check the running NocoDB version, for example in the admin panel or the image tag, and compare it with `2026.08.0`.

## Fix

- NocoDB: move to `2026.08.0` or later.

## Timeline

- 2026-11-13T10:47:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126280

## Documents

- [advisory] Vendor advisory: github.com https://github.com/nocodb/nocodb/security/advisories/GHSA-mh65-9xcf-vf8v
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/nocodb-before-2026.08.0-refresh-token-reuse-via-non-atomic-rotation

## From the sources

NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid authenticated session, and no reuse event is recorded.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_