chore(deps): Bump aiohttp from 3.14.0 to 3.14.1

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[depintel-bot]

depintel verdict: caution

Package: aiohttp 3.14.0 -> 3.14.1

_{review bdc81ac39034 · engine fb6bec6}

🔒 Security fix: this bump fixes GHSA-2fqr-mr3j-6wp8, GHSA-4fvr-rgm6-gqmc, GHSA-4m7w-qmgq-4wj5, GHSA-63hw-fmq6-xxg2 (+12 more) (per OSV). Merging is security-positive; this review took the full path because security fixes often carry behavioral hardening.

Impact: MODERATE — your code uses the changed symbol(s) (TCPConnector) and call-site analysis could not rule out the changed behavior (see exposure notes). Verify the flagged call sites against the findings before merging.

Basis is internally consistent: usage_scan found 1 touched symbol (TCPConnector) with 66 usage sites, exposure analysis ran (not skipped) and returned overall='possible' with a concrete call-site rationale showing plausible reachability via user-supplied URLs (proxybroker/judge.py). Since exposure is 'possible' rather than 'none', the de-escalation rule doesn't apply, and since it's not 'likely', escalation to breaking isn't warranted either. Security advisories (GHSA-*) justify the cautious posture. CI did-not-run is acknowledged as a gap but doesn't need to force escalation since the verdict already reflects incomplete confidence via 'caution'. No contradiction between verdict and basis.

Signal	Result
Version delta	patch
Repo usage scanned	yes (66 site(s))
Usage ∩ changed API	1
Static API findings	0
Release-note findings (LLM)	1
Changelog red-flag terms	3
Package type	import library
Dependency scope	runtime (pyproject [tool.poetry.dependencies])
CI on this PR	passing (15/15 checks green)

Basis: behavior change intersects usage; breaking requires positive exposure proof ('likely'), not intersection alone

Touched symbols:

• TCPConnector

Call-site exposure analysis: possible — 🟡 possible — cannot be ruled out from the visible code

• aiohttp.TCPConnector (proxybroker/judge.py:107) → possible [fails loudly (clear exception); requires spec-illegal input]: The TCPConnector here backs a ClientSession that connects directly to self.url, whose host is urlparse(url).netloc. self.url ultimately comes from Judge(j) where j is drawn from the judges list passed into get_judges()/Checker()/Broker(), which is a public API parameter that callers can supply arbitrary judge URLs to. Default judges are all canonical domain names, but the API does not validate/canonicalize the host before use, so a caller-supplied judge URL with a legacy numeric IPv4 host (e.g. 'http://127.1/') would flow unmodified into TCPConnector via aiohttp's URL host resolution. Since we cannot see all real-world call sites/configuration for Broker(judges=...), exposure cannot be ruled out.
• aiohttp.TCPConnector (proxybroker/resolver.py:214) → none: This connector is only ever used with URLs drawn from the hardcoded class attribute Resolver._ip_hosts (api64.ipify.org, wtfismyip.com, api.ipify.org, ipinfo.io, icanhazip.com, myexternalip.com, ifconfig.io). These are all canonical DNS hostnames, never legacy numeric IPv4 literal forms, and the list is not user-configurable at this call site. Since none of the candidate hosts are numeric IPv4 strings at all, the changed IPv4-literal-parsing behavior in TCPConnector cannot be triggered here.

Findings:

• aiohttp.TCPConnector (behavior_change, llm, confidence 0.95)
  • TCPConnector now rejects legacy non-canonical IPv4 host forms with InvalidUrlClientError instead of treating them as IP address literals.
  • Evidence: Changed :class:~aiohttp.TCPConnector to reject legacy non-canonical numeric IPv4 host forms such as 2130706433, 017700000001 and 127.1 with :exc:~aiohttp.InvalidUrlClientError; only canonical dotted-quad IPv4 literals are now treated as IP address literals, while every other host is sent through the configured resolver
  • Source: https://github.com/aio-libs/aiohttp/releases/tag/v3.14.1

---

Run: 20260804T150434Z-1e03a0242fe0

Evidence is static analysis plus release evidence available to depintel at run time. This advisory verdict is not a substitute for maintainer review.

[dependabot]

Superseded by #235.