CVE-2026-46550: NocoDB missing Secure and SameSite flags in refresh-token cookie

CVE-2026-46550 · Severity: medium · CVSS 5.4 · Published 2026-06-23

NocoDB is an open-source platform that turns databases into easy-to-use spreadsheets. A security flaw in how the application handles login sessions could allow attackers to intercept user credentials over unencrypted connections or trick a user's browser into performing unauthorized actions. This could lead to unauthorized access to sensitive database information or account takeover.

Technologies: nocodb (npm). Vendors: npm.

Quick answers

Is CVE-2026-46550 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46550 being exploited in the wild.
How severe is CVE-2026-46550?
Medium severity, with a CVSS score of 5.4, published 23 June 2026.
Which products and versions are affected?
nocodb (npm) <= 0.301.3, SEMVER:introduced=0,last_affected=0.301.3.
Is there a fix for CVE-2026-46550?
A patch was published on 2026-04-01: Fix released in version 2026.04.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46550 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46550?
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.

Technical details

NocoDB versions prior to 2026.04.1 fail to apply the 'Secure' flag and 'SameSite' attribute to the refresh-token cookie in the 'setTokenCookie' helper. Because the 'Secure' flag is missing, the cookie can be transmitted over unencrypted HTTP, making it vulnerable to network interception. Additionally, the absence of the 'SameSite' attribute allows browsers to include the cookie in cross-site POST requests, facilitating a Cross-Site Request Forgery (CSRF) attack against the '/api/v2/auth/token/refresh' endpoint. An attacker could potentially refresh a victim's session and, if combined with other vulnerabilities like XSS, capture the new JWT. The issue is resolved in version 2026.04.1 by implementing 'SameSite: lax' and conditional 'Secure' flags.

Affected products

  • NocoDB NocoDB < 2026.04.1

Identifiers

  • CVE-2026-46550
  • GHSA-f74w-272x-mqcv

Timeline

  • 2026-05-19: advisory: GitHub Security Advisory published
  • 2026-06-23: disclosed: CVE published to NVD
  • 2026-04-01: patched: Fix released in version 2026.04.1

References

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