NousResearch/hermes-agent

Cron provider key origin binding security fix

Cluster 126300. Data as of 2026-10-27 11:58 UTC

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

open issues

open PRs

items grouped

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

Next step: read #130611, then check it covers your case.

Read #130611 Pick up a Lab task

A bug where cron jobs matched stored provider keys against hostname only, allowing keys to be sent over HTTP, to different ports, or subdomains. The fix restricts key transmission to the provider's exact configured 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.

#130611 Cron jobs send a stored provider key only to that provider's configured origin, not over HTTP, another port or a subdomain (#126300, salvage #126306)

merged to main

files: hermes_cli/config_providers.py, tests/tools/test_cronjob_tools.py, tools/cronjob_job_args.py, website/docs/user-guide/features/cron.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/features/cron.md

1 PR closed without merging

From the close comments: merged via another change 1

#126306 fix(cron): bind a stored provider key to its configured origin, not its hostname · merged via another change → fb5cbcb, #130611

Closed issues · 1

Closed#126300[Bug]: cron base_url check matches the provider's hostname, not its origin (stored key can go over HTTP, to another port, or to a subdomain)

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: #130611
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 3 Oct 2026

For your agent

The same facts, typed.

cluster/126300.json
cluster/126300.md