Cairn
NousResearch/hermes-agent

Loopback host header validation fix for non-standard IPs

Cluster 39280 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

A bug where non-standard loopback addresses (e.g. 127.0.0.11) are rejected by host header middleware, causing delegate_task failures, along with corresponding fixes in the web server and dashboard to accept the full 127.0.0.0/8 loopback range.

Open issues1

  • Issue#39280[Bug]: delegate_task fails (HTTP 500) when gateway binds a non-standard loopback (e.g. 127.0.0.11) — host_header_middleware rejects subagent callbacks

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #39285 fix(web_server): accept full 127.0.0.0/8 loopback range in host header validation · done elsewhere
  • #39870 fix(dashboard): accept nonstandard loopback host headers · other → #39285, #39280
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.00 means 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 Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/39280.json
cluster/39280.md