Repository navigation
fix(session): Reject non-user access tokens in session cookies - #514
Merged
Merged
Conversation
verifyAccessToken now requires sid and auth_time, a sub_profile that is absent or user, and no sub_type, so other token types signed by the same environment key do not authenticate a session. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
Original prompt from madison.packer
|
Contributor
Devin Review🟢 Devin Review found nothing to fix · View findings · Follow Devin's work |
[High impact] The PR appears safe to merge; no actionable defects were found. SummaryThis PR rejects non-user access tokens before trusting or saving a session.
No actionable issues were found. Tests were not run.
|
nicknisi
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
verifyAccessTokeninsession.ts(used byupdateSession/withAuthandassertValidAccessToken) only ranjwtVerify: signature,exp, andisswhenWORKOS_ISSUERis set. It didn't check that the token was a user session access token, so other token types signed by the same environment key were accepted as a session.This matches
hasRequiredAccessTokenClaimsin@workos-inc/node.sub_profileis optional on user access tokens, so a missing claim is still accepted. A rejected token takes the existinginvalidpath: the cookie is deleted and no refresh is attempted, the same as a bad signature.Tests: a new
should reject a verified token with %s without attempting to refresh itcoverssub_profile: ai_agent,sub_type: authkit, a missing or stringauth_time, and a missing or numericsid. All 6 cases fail without thesession.tschange.Fixture plumbing: most specs mocked
jwtVerifyto resolveundefined,trueor{}. They now resolve the sharedverifiedUserAccessTokenfromtest-helpers.ts, andgenerateTestTokenincludesauth_timeby default.Link to Devin session: https://app.devin.ai/sessions/7e123fc2545a49c282b043a4abd58f70
Open in Devin Desktop: https://app.devin.ai/desktop/session/7e123fc2545a49c282b043a4abd58f70?variant=devin
Requested by: @m0tzy