CVE-2026-47379: NocoDB timing attack in shared-view password check

CVE-2026-47379 · Severity: medium · CVSS 4 · Published 2026-06-23

NocoDB, a platform that turns databases into smart spreadsheets, contained a flaw in how it verified passwords for shared views. For older accounts using legacy passwords, the system compared passwords in a way that allowed an attacker to guess the password by measuring how long the server took to respond. If exploited, an unauthorized person could gain access to private data shared via these spreadsheet views.

Technologies: nocodb (npm). Vendors: npm.

Quick answers

Is CVE-2026-47379 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47379 being exploited in the wild.
How severe is CVE-2026-47379?
Medium severity, with a CVSS score of 4, published 23 June 2026.
Which products and versions are affected?
nocodb (npm) <= 2026.05.0, ECOSYSTEM:introduced=0,fixed=2026.05.1.
Is there a fix for CVE-2026-47379?
Yes. nocodb (npm): upgrade to 2026.05.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47379 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47379?
Check whether you run nocodb (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • nocodb (npm): upgrade to 2026.05.1 or later
    npm install nocodb@2026.05.1

Technical details

A timing side-channel vulnerability exists in NocoDB's shared-view authentication mechanism. For legacy plaintext passwords (those not migrated to bcrypt), the application utilized strict-equality (===) comparison in View.ts and the EE dashboard model's verifyPassword function. Because strict equality returns early upon finding a mismatched character, an attacker can measure response times to determine the password's length and discover it character-by-character. The vulnerability is resolved in version 2026.05.1 by implementing crypto.timingSafeEqual and ensuring constant-time comparisons even during length mismatches.

Affected products

  • nocodb nocodb < 2026.05.1

Identifiers

  • CVE-2026-47379
  • GHSA-qhxg-623c-cfjm

Timeline

  • 2026-06-04: advisory: GitHub Security Advisory published
  • 2026-06-23: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.