
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Shellvoide Blog - AI-Powered Cybersecurity, Compliance &amp; Penetration Testing</title>
      <link>https://shellvoide.com/blog/blog</link>
      <description>The Shellvoide security blog: AI-driven penetration testing, vulnerability research, and application security insights from the team behind KLUE.</description>
      <language>en-us</language>
      <managingEditor>info@shellvoide.com (Shellvoide)</managingEditor>
      <webMaster>info@shellvoide.com (Shellvoide)</webMaster>
      <lastBuildDate>Wed, 04 Nov 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://shellvoide.com/blog/tags/token-confusion/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://shellvoide.com/blog/blog/nocodb-oauth-token-session-confusion</guid>
    <title>A Valet Key to the Whole House: NocoDB Accepted OAuth Tokens as Full Sessions</title>
    <link>https://shellvoide.com/blog/blog/nocodb-oauth-token-session-confusion</link>
    <description>NocoDB signed its OAuth access tokens with the same secret as its first-party session tokens, so a token a user granted for a narrow OAuth scope was accepted by the session strategy, the enterprise SSO-to-session exchange, and the realtime socket handshake as a fully logged-in browser. We walk the seam: why a validly signed JWT with no &#39;I am only a valet key&#39; marker sailed past every gate, the CWE-287 root cause, and the single distinction the 2026.10.1 fix finally draws. Reported and credited; tracked as GHSA-xmfr-pc8j-4xh5.</description>
    <pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate>
    <author>info@shellvoide.com (Shellvoide)</author>
    <category>nocodb</category><category>oauth</category><category>jwt</category><category>authentication</category><category>broken-authentication</category><category>token-confusion</category><category>session-management</category><category>cwe-287</category><category>vulnerability-research</category><category>case-study</category><category>disclosure</category><category>appsec</category>
  </item>

    </channel>
  </rss>
