<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T02:13:36.546332+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-330148</id>
    <title>EUVD-2026-330148</title>
    <updated>2026-10-07T02:13:36.594329+00:00</updated>
    <content>EUVD-2026-330148</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-330148"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53926</id>
    <title>fkie_cve-2026-53926</title>
    <updated>2026-10-07T02:13:36.594369+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, revokeAllOAuthTokensByUser in the users service is an empty stub being called from passwordChange, passwordForgot, and passwordReset. OAuth access and refresh tokens were not revoked when the user changed, reset, or recovered their password, leaving an attacker-issued OAuth grant valid after the user believed they had locked the attacker out. This vulnerability is fixed in 2026.05.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-53926"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-g72g-r7m4-9x4g</id>
    <title>GHSA-g72g-r7m4-9x4g — NocoDB: OAuth Tokens Persist Through Security Events</title>
    <updated>2026-10-07T02:13:36.594403+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nocodb</p>
<p>### Summary
OAuth access and refresh tokens were not revoked when the user changed, reset, or
recovered their password, leaving an attacker-issued OAuth grant valid after the user
believed they had locked the attacker out.</p>
<p>### Details
`revokeAllOAuthTokensByUser` in the users service was an empty stub being called from
`passwordChange`, `passwordForgot`, and `passwordReset`. It now delegates to
`OAuthToken.revokeAllByUser(userId)`, which deletes the rows and invalidates the
related auth caches. All three reset/recovery flows now consistently revoke refresh
tokens (GHSA-r989-7g3j-wjhw), OAuth tokens (this advisory), and rotate
`token_version`.</p>
<p>### Impact
Persistent unauthorized access through previously issued OAuth tokens after a
documented security event (password change, forgot, or reset).</p>
<p>### Credit
This issue was reported by [@bugbunny-research](https://github.com/bugbunny-research).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-g72g-r7m4-9x4g"/>
  </entry>
</feed>
