OAuth PKCE state and code_verifier conflation security fix
Cluster 10693. Data as of
Nothing open on GitHub. Fix merged in #26861 on 16 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #26861. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #26861. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members concern a security vulnerability where the OAuth PKCE code_verifier was incorrectly reused as the state parameter, leaking it via the authorization URL. The group includes the bug report, fixes separating the two values, and related cleanup of an unused PKCE flow.
Open issues0
Open PRs0
Fixes on record
-
#26861 fix(security): separate OAuth PKCE state from code_verifier (#10693)
files:
agent/anthropic_adapter.py,scripts/release.py,tests/agent/test_anthropic_oauth_pkce.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#10699 fix(security): separate OAuth PKCE state from code_verifier · merged via another change →
#26861,#1775,#2647,#3107,#10699
Closed issues · 1
- Closed#10693OAuth PKCE code_verifier reused as state parameter — verifier leaked via authorization URL
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #26861
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 May 2026