Skip to main content
VulnerabilityPublished Updated

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

Affects nocodbSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.301.3 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.301.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade nocodb to 0.301.3.

Affected software

ProductAffectedFixed in
npmnocodbAffected
  • <0.301.3
Fixed in
  • 0.301.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade NocoDB to version 0.301.3 or later, where the password reset flow properly revokes all existing refresh tokens. Applying this official fix ensures that stolen refresh tokens are invalidated upon password reset, preventing continued unauthorized access.

Description

NocoDB versions prior to 0.301.3 have a vulnerability where the password reset process does not revoke existing refresh tokens. This allows an attacker who has previously stolen a refresh token to continue generating valid JWTs even after the victim resets their password. The issue was fixed in version 0.301.3.

References

Community reviews

Loading reviews…