Medium · CVSS 0.0CVE-2026-28396GHSA-X4VH-J75G-268G

NocoDB's Refresh Tokens Not Revoked on Password ResetCVE-2026-28396

Answer in brief

CVE-2026-28396 records a Medium severity (CVSS 0.0) vulnerability in NocoDB's Refresh Tokens Not Revoked on Password Reset. The current sources do not mark it as known exploited. The current feed maps nocodb (npm), nocodb (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 2, 2026Updated Nov 5, 2026Source checked Nov 5, 2026First seen by HOL Nov 5, 2026Material review Nov 5, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 0.0
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nocodb (npm), nocodb (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nocodbnpm	<=0.301.2	0.301.3
nocodbnpm	>=0 <0.301.3	0.301.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for nocodb, nocodb.
Review the reported fix. Update nocodb to 0.301.3; nocodb to 0.301.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 2, 2026
Evidence: source:ghsa:source_dates:source-dates:record
Source modified
Nov 5, 2026
Evidence: source:ghsa:source_dates:source-dates:record
First seen by HOL
Nov 5, 2026

Sources and claim methodology

Upstream source description

### 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 `token_version` (invalidating JWTs) but did not call `UserRefreshToken.deleteAllUserToken()`. The `refreshToken()` method only checked token existence, not `token_version`. 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](https://github.com/bugbunny-research) (bugbunny.ai).

Quoted source text, attributed separately from HOL analysis.