4.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-28396

CVE-2026-28396: NocoDB: Refresh Tokens Not Revoked on Password Reset

NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, 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. This issue has been patched in version 0.301.3.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-28396

CVE-2026-28396:

4.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
nocodb	npm	<= 0.301.2	0.301.3

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the password reset functionality of NocoDB. The advisory explicitly mentions that the passwordReset() function in users.service.ts did not revoke existing refresh tokens. By analyzing the commits between the vulnerable version 0.301.2 and the patched version 0.301.3, I identified the security patch in commit dfbe836577354ba780563a5cf8cb50bfc61a203e. The patch adds a call to UserRefreshToken.deleteAllUserToken(user.id) within the passwordReset function in packages/nocodb/src/services/users/users.service.ts. This confirms that UsersService.passwordReset is the vulnerable function. When this function is called during a password reset, it previously left refresh tokens active, allowing an attacker with a stolen token to maintain access.

Vulnerable functions

UsersService.passwordReset

packages/nocodb/src/services/users/users.service.ts

The `passwordReset` function in `users.service.ts` was responsible for handling the password reset flow. Before the patch, this function would update the `token_version` to invalidate JWTs, but it failed to revoke existing refresh tokens. This was because it did not call `UserRefreshToken.deleteAllUserToken()`. An attacker with a stolen refresh token could therefore continue to mint new, valid JWTs even after the user reset their password. The patch fixes this by adding the call to `UserRefreshToken.deleteAllUserToken(user.id)`.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.