Cairn
NousResearch/hermes-agent

Slack approval buttons bound to secure tokens

Cluster 80283 · 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 concern where Slack approval and slash-confirm buttons relied on client-supplied session keys rather than opaque or server-bound tokens. The changes introduce binding of approval buttons to exact requests or opaque tokens to add defense-in-depth.

Open issues1

  • Issue#80283Security: Slack approval session_key taken from client payload (no defense-in-depth)

Open PRs1

  • PR#82025fix(slack): bind approval buttons to exact requests (#80283)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #81748 fix(slack): bind approval and slash-confirm buttons to opaque tokens · superseded by another PR → #82025
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/80283.json
cluster/80283.md