https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 07:21:17 +0000 https://cve.radiocsirt.org/vuln/cnvd-2026-13836 cnvd-2026-13836 https://cve.radiocsirt.org/vuln/cnvd-2026-13836 https://cve.radiocsirt.org/vuln/euvd-2026-274086 EUVD-2026-274086 https://cve.radiocsirt.org/vuln/euvd-2026-274086 https://cve.radiocsirt.org/vuln/fkie_cve-2026-28396 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-28396 https://cve.radiocsirt.org/vuln/ghsa-x4vh-j75g-268g <p><strong>Affected:</strong> npm: nocodb</p> <p>### 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.</p> <p>### 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.</p> <p>### Impact An attacker who previously obtained a refresh token retains access after password reset until the token expires.</p> <p>### Credit This issue was reported by [@bugbunny-research](https://github.com/bugbunny-research) (bugbunny.ai).</p> <p><strong>Affected:</strong> npm: nocodb</p> <p>### 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.</p> <p>### 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.</p> <p>### Impact An attacker who previously obtained a refresh token retains access after password reset until the token expires.</p> <p>### Credit This issue was reported by [@bugbunny-research](https://github.com/bugbunny-research) (bugbunny.ai).</p> https://cve.radiocsirt.org/vuln/ghsa-x4vh-j75g-268g