url_safety SSRF check handling of DNS failures in sandboxes
Cluster 32217 · agent. Data as of
Nothing open on GitHub. Fix merged in #70874 on 24 Jul 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 #70874. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #70874. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Members concern the url_safety/SSRF check and how it behaves when DNS resolution is unavailable, such as in proxy or sandbox environments (including NVIDIA OpenShell) or when allow_private_urls is enabled. They include one issue report and several proposed changes to permit DNS failure; one is described as a salvage of an earlier PR.
Open issues0
Open PRs0
Fixes on record
-
#70874 fix(url_safety): allow DNS failure in proxy/sandbox environments (salvage of #68469 by @kuangmi-bit)
files:
contributors/emails/[redacted:email],tests/tools/test_url_safety.py,tools/url_safety.py
2 PRs closed without merging
From the close comments: merged via another change 1 · stale or abandoned 1
Closed issues · 1
- Closed#32217SSRF check blocks web tools inside NVIDIA OpenShell sandbox (DNS unavailable by design)
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
- #70874
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 24 Jul 2026