Cairn
NousResearch/hermes-agent

Bind clarify resolution to owning session key

Cluster 87780 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 1 PR.

These items address a security issue where clarify resolution in the gateway could be triggered using a forged or guessed clarify_id without verifying session, chat, or profile ownership. The fixes enforce that clarify resolution is bound to the owning session key.

Open issues1

  • Issue#87780security: resolve_gateway_clarify() accepts a forged/guessed clarify_id with no session/chat/profile binding

Open PRs1

  • PR#130816fix(gateway): bind clarify resolution to the owning session

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #87791 fix(gateway): bind clarify resolve to owning session_key · stale or abandoned
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/87780.json
cluster/87780.md