Cairn
NousResearch/hermes-agent

API key leaking to unintended origins via hostname match

Cluster 126218. Data as of

Nothing open on GitHub. Fix merged in #130508 on 3 Oct 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #130508. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #130508. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where an API key bound to a specific OPENAI_BASE_URL could be incorrectly sent to other services sharing the same hostname but using a different scheme or port. The associated fix and follow-up work tighten key routing so each key is sent only to its exact origin.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #130508 Auxiliary clients and the OpenRouter mirror send the main or OPENAI_BASE_URL-bound API key only to its exact origin (#126104, #126218, salvage #126108, #126222)

    merged to main

    files: agent/auxiliary_client.py, hermes_cli/runtime_provider_backends.py, tests/agent/test_auxiliary_client.py, tests/agent/test_auxiliary_ollama_local_provider.py, tests/hermes_cli/test_runtime_provider_resolution.py, website/docs/reference/environment-variables.md, website/docs/user-guide/configuration.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/environment-variables.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/configuration.md

1 PR closed without merging

From the close comments: other 1

  • #126222 fix(runtime_provider): an OPENAI_BASE_URL-bound OPENAI_API_KEY follows its origin, not its hostname · other → #130508
Closed issues · 1
  • Closed#126218[Bug]: an OPENAI_BASE_URL-bound OPENAI_API_KEY reaches an OpenRouter mirror on the same hostname over http:// or another port
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

Merged PRs
#130508
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
3 Oct 2026

For your agent

The same facts, typed.

cluster/126218.json
cluster/126218.md