CVE-2026-46550: NocoDB Refresh Token Cookie Set Without Vulnerability

MODERATE
Advisory Identifier: GHSA-f74w-272x-mqcv
Share
CVSS 5.4
CWE-614
Published
Advisory Summary

CVE-2026-46550 is a MODERATE (CVSS 5.4) refresh token cookie set without vulnerability (CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute) affecting NocoDB libraries in the npm ecosystem. The issue involves refresh token cookie set without `secure` and `samesite` flags. Remediation is available in the latest vendor maintenance releases.

CVE-2026-46550 at a Glance

CVE Identifier CVE-2026-46550
GHSA Identifier GHSA-f74w-272x-mqcv
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Affected Product NocoDB
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-46550

To remediate this vulnerability, upgrade all affected NocoDB dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nocodb fixed: Latest secure release 
npm install nocodb@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls nocodb

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-46550, inspect your project dependencies using npm:

npm ls nocodb

Analyze the terminal output to locate any version of NocoDB in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls nocodb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute, where the secure attribute for sensitive cookies in https sessions is not set. In NocoDB, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The refresh-token cookie was set with `httpOnly: true` but missing both the `secure` flag and the `sameSite` attribute. Over plain HTTP the cookie could be intercepted on the network; without `sameSite`, browsers attached it to cross-site POSTs, enabling CSRF against the token-refresh endpoint. ### Details In `packages/nocodb/src/services/users/helpers.ts`, `setTokenCookie` produced the cookie with only `httpOnly`, an `expires` date, and an optional `domain` from `NC_BASE_HOST_NAME` — no `secure`, no `sameSite`. The refresh endpoint `POST /api/v2/auth/token/refresh` (`auth.controller.ts`) read the cookie unconditionally and returned a new JWT, with no CSRF token. The fix sets `httpOnly: true`, `sameSite: 'lax'`, and conditional `secure: req.ncSiteUrl.startsWith('https')` so the flag is active under HTTPS while still functional on plain-HTTP localhost development. This is distinct from GHSA-x4vh-j75g-268g (refresh-token lifecycle on password reset) — different root cause, different attack vector. ### Impact - Cookie interception on plain HTTP networks (no `secure`). - Cross-site refresh: malicious cross-origin pages could trigger token refresh and, combined with any same-origin XSS or open-redirect on the NocoDB domain, capture the new JWT. - Refresh tokens have multi-day expiry (`NC_REFRESH_TOKEN_EXP_IN_DAYS`), so the exposure window is long. ### Credit This issue was reported by [@ik0z](https://github.com/ik0z).

CVE-2026-46550 Affected NocoDB Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
nocodb
npm/nocodb
npm
≤ 0.301.3

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nocodb/nocodb/security/advisories/GHSA-f74w-272x-mqcv
NVD — CVE-2026-46550 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-46550
NocoDB Source Repository REPOSITORY
https://github.com/nocodb/nocodb

Frequently Asked Questions

What is CVE-2026-46550?
CVE-2026-46550 is a security vulnerability in NocoDB involving Refresh Token Cookie Set Without `secure` and `sameSite` Flags under CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute.
Which NocoDB versions are affected?
Affected versions include releases prior to current release patches across affected packages: nocodb.
What version fixes CVE-2026-46550?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is nocodb affected?
Yes, nocodb is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-46550?
CVE-2026-46550 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-46550?
CVE-2026-46550 is classified under CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (The Secure attribute for sensitive cookies in HTTPS sessions is not set.).
How can I check npm dependencies for CVE-2026-46550?
Run the dependency tree command: 'npm ls nocodb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f74w-272x-mqcv",
  "modified" : "2026-07-20T21:16:17Z",
  "published" : "2026-05-21T20:35:24Z",
  "aliases" : [ "CVE-2026-46550" ],
  "summary" : "NocoDB: Refresh Token Cookie Set Without `secure` and `sameSite` Flags",
  "details" : "### Summary\n\nThe refresh-token cookie was set with `httpOnly: true` but missing both the `secure` flag and the `sameSite` attribute. Over plain HTTP the cookie could be intercepted on the network; without `sameSite`, browsers attached it to cross-site POSTs, enabling CSRF against the token-refresh endpoint.\n\n### Details\n\nIn `packages/nocodb/src/services/users/helpers.ts`, `setTokenCookie` produced the cookie with only `httpOnly`, an `expires` date, and an optional `domain` from `NC_BASE_HOST_NAME` — no `secure`, no `sameSite`. The refresh endpoint `POST /api/v2/auth/token/refresh` (`auth.controller.ts`) read the cookie unconditionally and returned a new JWT, with no CSRF token.\n\nThe fix sets `httpOnly: true`, `sameSite: 'lax'`, and conditional `secure: req.ncSiteUrl.startsWith('https')` so the flag is active under HTTPS while still functional on plain-HTTP localhost development.\n\nThis is distinct from GHSA-x4vh-j75g-268g (refresh-token lifecycle on password reset) — different root cause, different attack vector.\n\n### Impact\n\n- Cookie interception on plain HTTP networks (no `secure`).\n- Cross-site refresh: malicious cross-origin pages could trigger token refresh and, combined with any same-origin XSS or open-redirect on the NocoDB domain, capture the new JWT.\n- Refresh tokens have multi-day expiry (`NC_REFRESH_TOKEN_EXP_IN_DAYS`), so the exposure window is long.\n\n### Credit\n\nThis issue was reported by [@ik0z](https://github.com/ik0z).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nocodb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.301.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nocodb/nocodb/security/advisories/GHSA-f74w-272x-mqcv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46550"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nocodb/nocodb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-614" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-21T20:35:24Z",
    "nvd_published_at" : "2026-06-23T21:16:58Z"
  }
}