CVE-2026-126280

Description

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.

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

• 9.1CVSS 4.0, Criticalfrom the CNA (VulnCheck)CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
• 7.4CVSS 3.1, Highfrom the CNA (VulnCheck)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

Timeline

1. 13 Nov 2026 Published

Weakness

• CWE-362

References

• GitHub Security Advisory (GHSA-mh65-9xcf-vf8v)vendor-advisory
• VulnCheck Advisory: NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotationthird-party-advisory