- Published on
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 'I am only a valet key' 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.