<?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-04T16:59:20.787938+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-329769</id>
    <title>EUVD-2026-329769</title>
    <updated>2026-10-04T16:59:20.791263+00:00</updated>
    <content>EUVD-2026-329769</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329769"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46554</id>
    <title>fkie_cve-2026-46554</title>
    <updated>2026-10-04T16:59:20.791296+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.04.4, deleted API tokens continued to authenticate requests until their cache entry expired, because the auth cache was not invalidated by token value at deletion time. The API token deletion path removed the database row but did not evict the token-value keyed entry from the auth cache. The auth middleware therefore continued to accept the deleted token until the cache entry aged out, leaving a deletion-to-revocation window of up to three days. This vulnerability is fixed in 2026.04.4.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-46554"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-f76x-f9vj-92jv</id>
    <title>GHSA-f76x-f9vj-92jv — NocoDB: Stale Auth Cache After API Token Deletion</title>
    <updated>2026-10-04T16:59:20.791331+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nocodb</p>
<p>### Summary
Deleted API tokens continued to authenticate requests until their cache entry expired, because the auth cache was not invalidated by token value at deletion time.</p>
<p>### Details
The API token deletion path removed the database row but did not evict the token-value keyed entry from the auth cache. The auth middleware therefore continued to accept the deleted token until the cache entry aged out, leaving a deletion-to-revocation window of up to three days.</p>
<p>### Impact
Tokens revoked through the UI or API continued to grant access during the cache TTL, breaking the operator's expected security guarantee that deletion is immediate.</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-f76x-f9vj-92jv"/>
  </entry>
</feed>
