NousResearch/hermes-agent

RPC token exposure and kernel dir permissions

Cluster 121932. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #124262 on 26 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #124262, then check it covers your case.

Read #124262 Pick up a Lab task

These issues and PRs concern sensitive RPC token data appearing in process arguments or session snapshots, and kernel/RPC directories being accessible to other users on shared systems. The work focuses on restricting directory permissions and removing the token from remote argv.

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.

#124262 fix(code-execution): keep the RPC token out of remote argv and lock down kernel dirs

merged to main

files: tests/tools/_child_env_fixtures.py, tests/tools/test_code_execution.py, tests/tools/test_code_execution_file_rpc.py, tests/tools/test_code_kernel_remote.py, tests/tools/test_tool_result_storage.py, tools/code_execution_rpc.py, tools/code_execution_tool.py, tools/code_kernel_remote.py, tools/environments/base_session_env.py, tools/tool_result_storage.py

2 PRs closed without merging

From the close comments: done elsewhere 2

#121936 fix(code-execution): lock down remote kernel/RPC dirs, keep RPC token out of argv · done elsewhere → 7eed2de, #124262
#122440 fix(code-execution): keep the RPC token out of remote argv and the session snapshot · done elsewhere → bbc8a7d, #122072, #122073

Closed issues · 1

Closed#121932Remote execute_code drops the RPC token and tool data in world/group-accessible paths on shared backends

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

Merged PRs: #124262
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 26 Sep 2026

For your agent

The same facts, typed.

cluster/121932.json
cluster/121932.md