A2A no-token mode: reject browser-originated requests
Cluster 126141 · acp. Data as of
Nothing open on GitHub. Fix merged in #145310 on 27 Oct 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 #145310. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #145310. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Three members concern the A2A listener in no-token mode accepting browser-originated requests: one bug report and two fix proposals. One fix targets browser-originated POSTs, and the other also covers foreign-Host requests.
Open issues0
Open PRs0
Fixes on record
-
#145310 fix(a2a): refuse browser-originated and foreign-Host requests in no-token mode
files:
plugins/platforms/a2a/README.md,plugins/platforms/a2a/adapter.py,plugins/platforms/a2a/security.py,tests/plugins/test_a2a_no_token_guards.py,tests/plugins/test_a2a_plugin.py,website/docs/user-guide/messaging/a2a.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#126143 fix(a2a): refuse browser-originated POSTs in no-token mode · superseded by another PR →
#145310
Closed issues · 1
- Closed#126141[Bug]: A2A listener in no-token mode accepts browser-originated requests
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
- Subsystem
- acp
- Merged PRs
- #145310
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Oct 2026