NocoDB's Refresh Tokens Not Revoked on Password Reset

Exploitation

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

CVSS 4.0

4.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

• CVE-2026-28396: 0.21% estimated exploitation activity in the next 30 days; percentile 11.31 (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 password reset flow did not revoke existing refresh tokens, allowing an attacker with a previously stolen refresh token to continue minting valid JWTs after the victim resets their password. Details passwordReset() in users.service.ts updated tokenversion (invalidating JWTs) but did not call UserRefreshToken.deleteAllUserToken(). The refreshToken() method only checked token existence, not tokenversion. Both passwordChange() and signOut() correctly deleted all refresh tokens. Impact An attacker who previously obtained a refresh token retains access after password reset until the token expires. Credit This issue was reported by @bugbunny-research (bugbunny.ai).

Published by the source

2 Mar 2026, 19:53 UTC

Last modified by the source

4 Mar 2026, 15:17 UTC

Source last checked

26 Oct 2026, 12:42 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x4vh-j75g-268g

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x4vh-j75g-268g

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

# Patch Next advisory brief: CVE-2026-28396

Advisory: NocoDB's Refresh Tokens Not Revoked on Password Reset
IDs: CVE-2026-28396, GHSA-x4vh-j75g-268g
Record: https://patchnext.com/advisories/cve-2026-28396 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nocodb 0.301.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected <= 0.301.2; fixed in 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
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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-x4vh-j75g-268g (OSV record GHSA-x4vh-j75g-268g lists affected ranges: npm nocodb >=0 <0.301.3 (fixed))
- Verified: https://github.com/advisories/GHSA-x4vh-j75g-268g (GitHub-reviewed advisory GHSA-x4vh-j75g-268g lists affected ranges: npm nocodb >=0 <=0.301.2)

Commands are suggestions: review each one before running it.