https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 21:47:42 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-330030 EUVD-2026-330030 https://cve.radiocsirt.org/vuln/euvd-2026-330030 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46550 <p>NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, 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. This vulnerability is fixed in 2026.04.1.</p> <p>NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, 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. This vulnerability is fixed in 2026.04.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46550 https://cve.radiocsirt.org/vuln/ghsa-f74w-272x-mqcv <p><strong>Affected:</strong> npm: nocodb</p> <p>### Summary</p> <p>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.</p> <p>### Details</p> <p>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.</p> <p>The fix sets `httpOnly: true`, `sameSite: &#39;lax&#39;`, and conditional `secure: req.ncSiteUrl.startsWith(&#39;https&#39;)` so the flag is active under HTTPS while still functional on plain-HTTP localhost development.</p> <p>This is distinct from GHSA-x4vh-j75g-268g (refresh-token lifecycle on password reset) — different root cause, different attack vector.</p> <p>### Impact</p> <p>- 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.</p> <p>### Credit</p> <p>This issue was reported by [@ik0z](https://github.com/ik0z).</p> <p><strong>Affected:</strong> npm: nocodb</p> <p>### Summary</p> <p>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.</p> <p>### Details</p> <p>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.</p> <p>The fix sets `httpOnly: true`, `sameSite: &#39;lax&#39;`, and conditional `secure: req.ncSiteUrl.startsWith(&#39;https&#39;)` so the flag is active under HTTPS while still functional on plain-HTTP localhost development.</p> <p>This is distinct from GHSA-x4vh-j75g-268g (refresh-token lifecycle on password reset) — different root cause, different attack vector.</p> <p>### Impact</p> <p>- 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.</p> <p>### Credit</p> <p>This issue was reported by [@ik0z](https://github.com/ik0z).</p> https://cve.radiocsirt.org/vuln/ghsa-f74w-272x-mqcv