CVE-2026-28396
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNocoDB 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn NocoDB prior to version 0.301.3, the password reset functionality fails to revoke existing refresh tokens. An attacker who has previously stolen a valid refresh token can continue using it to mint new JWT access tokens even after the victim resets their password, maintaining unauthorized access to the victim's account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.301.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed NocoDB versionCheck the version of NocoDB running in your environment. This is typically visible in the UI footer, or can be obtained via API endpoint /api/v1/version, or by inspecting package.json if you have access to the deployment files.Affected if The installed version is any version prior to 0.301.3 (e.g., 0.300.0, 0.250.0, etc.)
-
Verify password reset functionality is enabledConfirm that password reset / forgot password feature is enabled in your NocoDB instance. This is typically configured in the authentication settings or environment variables (look for SMTP or email-related configuration that enables password reset emails).Affected if Password reset is enabled and you are running a version < 0.301.3
-
Check for active user sessionsInspect your database for active refresh tokens in the nc_refresh_tokens or similar sessions table. Query for recent entries to identify users who have active authenticated sessions.Affected if There are active refresh tokens in the system and the NocoDB version is < 0.301.3 - these tokens would NOT be revoked upon password reset
You are affected if your NocoDB installation version is less than 0.301.3 and you have users who have used the password reset functionality while having active sessions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.301.3
Upgrade to NocoDB version 0.301.3 or later which includes the patch. As a precautionary measure, consider manually invalidating all active sessions for users who have recently reset their passwords.
0.301.3
- Upgrade Nocodb to version 0.301.3 or later to apply the security patch that revokes refresh tokens during password reset
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28396 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data