Cairn

Session key path-safety handling for chat integrations

NousResearch/hermes-agent · cluster 55617 · gateway

Data as of

Nothing open on GitHub. Fix merged in #59533. Check it covers your case.

The short answer

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

These issues and PRs concern how session keys containing slashes or other path-unsafe characters (notably from DingTalk DM and Google Chat) are handled, with proposals ranging from encoding those characters to relaxing or removing the filesystem path traversal guard.

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.

  • #59533 fix(gateway): relax session_key traversal guard to allow interior '/' (#59322)

    merged to main

    files: gateway/session.py, tests/gateway/test_session.py

5 PRs closed without merging

From the close comments: superseded by another PR 4 · done elsewhere 1

  • #55628 fix(gateway): encode path-unsafe chars in session key for DingTalk DMs · done elsewhere → 83f14b2, #55617
  • #55668 fix(gateway): allow slash in session_key for DingTalk DM sessions · superseded by another PR → 83f14b2, #59533
  • #55693 fix(gateway): encode unsafe session key components · superseded by another PR → 83f14b2, #59533
  • #55740 fix(gateway): percent-encode path separators in session key IDs (fixes DingTalk DM session loss on restart) · superseded by another PR → 83f14b2, #59533
  • #59458 fix: stop validating session_key as filesystem path (#59322) · superseded by another PR → 83f14b2, #59431, #59533
Closed issues · 2
  • Closed#55617DingTalk DM session_key rejected as directory traversal due to slash in chat_id
  • Closed#59322session_key traversal guard rejects all Google Chat sessions on load (v0.18.0)
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.26: 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
Merged PRs
#59533
Closed issues
2
Attempts
5 PRs closed without merging
Fix link checked
6 Jul 2026

For your agent

The same facts, typed.

cluster/55617.json
cluster/55617.md