CVE
NocoDB account takeover via unrevoked password reset links
Affects NocoDB before 2026.04.1 when a password is changed in the app while an earlier reset link is still unexpired. Fixed in 2026.04.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.04.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Password is changed from within the application (the in-app password-change path) An earlier password-reset link is still unexpired
Summary
NocoDB before 2026.04.1 fails to clear reset_password_token and reset_password_expires in users.service.ts when a password is changed, leaving earlier reset links valid. Attackers holding an unexpired reset link, such as from prior mailbox access, can set a new password and regain control of the account.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Password is changed from within the application (the in-app password-change path) An earlier password-reset link is still unexpiredUpgrade to a fixed version: 2026.04.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130717 (NocoDB before 2026.04.1 Password Reset Token Not Invalidated on Password Change), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130717 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.04.1
Fixed versions: 2026.04.1.
Conditions (all must be true for the bug to be hit):
- Password is changed from within the application (the in-app password-change path) (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-82pm-w64f-8m6h)
- An earlier password-reset link is still unexpired (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-82pm-w64f-8m6h)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-130717 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130717 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-82pm-w64f-8m6h
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130717
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130717"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.04.1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-82pm-w64f-8m6h |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130717 |
| Record | NVD · CVE-2026-130717 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130717
Is CVE-2026-130717 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
After a password is changed in the app, a password-reset link issued before the change still works. Anyone holding that link can set a new password and regain control of the account.Source: github.com
Which versions are affected by CVE-2026-130717?
nocodb: before 2026.04.1.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.04.1 are affected. The issue needs a password change made through the in-app password-change path while an earlier reset link has not yet expired. To check the installed version, compare it with 2026.04.1.Source: github.com
How do I fix CVE-2026-130717?
Upgrade NocoDB to 2026.04.1 or later, the fixed version in the product range. The checked facts name no vendor patch ids or workaround.Source: github.com