SSRF guard for browser/terminal backend scenarios
Cluster 38690 · agent. Data as of
Nothing open on GitHub. Fix merged in #50002 on 21 Jun 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #50002. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #50002. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern applying or enabling SSRF URL validation when the terminal runs in a container or uses a local browser backend. The discussion includes whether the local backend detection logic correctly accounts for terminal backend configuration.
Open issues0
Open PRs0
Fixes on record
-
#50002 fix(browser): enable SSRF guard when terminal runs in container (#38690)
files:
tests/tools/test_browser_ssrf_local.py,tools/browser_tool.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#38690`_is_local_backend()` doesn't consider terminal.backend — intentional?
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.50: 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
- agent
- Merged PRs
- #50002
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 21 Jun 2026