NocoDB: Refresh Token Cookie Set Without secure and sameSite Flags

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-46550: 0.16% estimated exploitation activity in the next 30 days; percentile 5.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 NCBASEHOSTNAME — 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…

Published by the source

21 May 2026, 20:35 UTC

Last modified by the source

20 Jul 2026, 21:30 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f74w-272x-mqcv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f74w-272x-mqcv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46550

Advisory: NocoDB: Refresh Token Cookie Set Without `secure` and `sameSite` Flags
IDs: CVE-2026-46550, GHSA-f74w-272x-mqcv
Record: https://patchnext.com/advisories/cve-2026-46550 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected <= 0.301.3

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f74w-272x-mqcv (OSV record GHSA-f74w-272x-mqcv lists affected ranges: npm nocodb >=0 <=0.301.3)
- Verified: https://github.com/advisories/GHSA-f74w-272x-mqcv (GitHub-reviewed advisory GHSA-f74w-272x-mqcv lists affected ranges: npm nocodb >=0 <=0.301.3)

Commands are suggestions: review each one before running it.