Cairn
NousResearch/hermes-agent

Block ambient cloud credentials in multiplexed profiles

Cluster 116313. Data as of

Nothing open on GitHub. Fix merged in #116963 on 20 Sep 2026. Check it covers your case.

The short answer

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

These issues and PRs address a security concern where multiplexed profiles could inherit or mint cloud credentials (Azure/AWS) from the launch profile's ambient credential chain. The work focuses on refusing or isolating such credential access when a multiplexed profile lacks its own explicit credentials.

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.

  • #116963 fix(agent): multiplexed profiles without their own Azure/AWS credentials are refused instead of minting the launch identity (#116313, salvage #116317)

    merged to main

    files: agent/azure_identity_adapter.py, agent/bedrock_adapter.py, tests/agent/test_azure_identity_adapter.py, tests/agent/test_bedrock_adapter.py, website/docs/developer-guide/multiplexing-gateway.md, website/docs/guides/azure-foundry.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #116317 fix(agent): refuse ambient credential chains for multiplex profiles · merged via another change → 297ebd5, #116963, #116313, #116317
  • #116370 fix(agent): isolate ambient cloud credentials across multiplexed profiles · done elsewhere → 297ebd5, #116963, #116313, #116317
Closed issues · 1
  • Closed#116313Multiplexed profiles can mint the launch profile's ambient Azure/AWS credential chain
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.50: 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
#116963
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/116313.json
cluster/116313.md