Cairn
NousResearch/hermes-agent

Gateway profile secret scope authorization fixes

Cluster 93522. Data as of

Nothing open on GitHub. Fix merged in #93639 on 24 Aug 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 #93639. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #93639. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug and related fixes addressing multiplexed and secondary profile authorization reads that bypass or leak across profile secret scopes in the gateway, covering platforms including weixin, yuanbao, wecom, and signal.

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.

  • #93639 fix(gateway): secondary-profile allowlists work and allow-all no longer leaks across profiles (#93522, salvage #93545 + #93605)

    merged to main

    files: gateway/platforms/signal.py, gateway/platforms/weixin.py, gateway/platforms/yuanbao.py, gateway/run.py, plugins/platforms/wecom/adapter.py, tests/gateway/test_multiplex_profile_authz.py, tests/gateway/test_platform_authz_scope.py, tests/gateway/test_wecom.py, tests/gateway/test_weixin_secret_scope.py, tests/gateway/test_yuanbao_secret_scope.py

2 PRs closed without merging

From the close comments: merged via another change 2

  • #93545 fix(gateway): scope multiplex-profile authorization reads (weixin/yuanbao/wecom) · merged via another change → #93639, #93605
  • #93605 fix(gateway): route platform authorization reads through the profile secret scope · merged via another change → #93639, #93545
Closed issues · 1
  • Closed#93522[Bug]: Multiplexed-profile authorization reads bypass the profile secret scope (weixin / yuanbao / signal / wecom)
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
#93639
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Aug 2026

For your agent

The same facts, typed.

cluster/93522.json
cluster/93522.md