Cross-profile session data leakage via bare session ID
NousResearch/hermes-agent · cluster 106761
Data as of
Nothing open on GitHub. Fix merged in #108074. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #108074. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #108074. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug allows bare session ID lookups to silently scan and return data from other profiles' state databases. Multiple fixes address stopping cross-profile reads and failing closed when a bare session ID resolves to a different profile.
Open issues0
Open PRs0
Fixes on record
-
#108074 Sessions no longer bind to or read another profile's state.db (#102526, #106761, #105887, #106974; salvage #102534, #106975)
files:
agent/turn_explainers.py,agent/turn_finalizer.py,evals/session_search_schema/runner.py,hermes_cli/profiles.py,hermes_state_registry.py,tests/hermes_cli/test_deleted_profile_tombstone.py,tests/hermes_state/test_shared_session_db_registry.py,tests/run_agent/test_corruption_recovery_guidance.py,tests/tools/test_session_search.py,tests/tui_gateway/test_launch_db_home_override_race.py,tests/tui_gateway/test_session_resume_db_ownership.py,tools/session_search_tool.py,tui_gateway/server.py
3 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1 · other 1
- #106768 fix(session_search): do not scan other profiles for bare session_id · done elsewhere
-
#106772 fix(session_search): stop cross-profile reads on a bare session id miss · other →
#106768,#106773,#106761 -
#106773 fix(tools): fail closed when a bare session id resolves into another profile · superseded by another PR →
#108074,#106761
Closed issues · 1
- Closed#106761session_search: reading a session by bare ID silently scans every profile's state.db and returns another profile's full transcript
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #108074
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 11 Sep 2026