# NousResearch/hermes-agent · Pin patched Starlette for CVE-2026-48710 (BadHost)

## Open now

- Nothing open on GitHub.

The three members all concern pinning a patched Starlette version in response to CVE-2026-48710, referred to as BadHost. One title specifies a minimum of 1.0.1; the titles alone do not show whether any of these changes were merged or shipped.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #35118. Verify it addresses your case.
- **Recommended:** read PR #35118 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-35118`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #35067: security: pin patched Starlette for CVE-2026-48710 BadHost

## Prior & competing PRs

- **#35118: security: pin patched Starlette (>=1.0.1) for CVE-2026-48710 BadHost**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `pyproject.toml`, `tests/test_packaging_metadata.py`, `tools/lazy_deps.py`
- **#35068: fix(deps): pin patched Starlette for CVE-2026-48710**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#35118`, `#35067`

## Fix status

- Merged to main in PR #35118 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-30`.