Evidence record / hermes-agent
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.
2026-07-01-hermes-agent-path-traversal-fix-model-supplied-tool-call-ids-could-es
Path-traversal fix: model-supplied tool-call IDs could escape the tool-result storage directory (channel: main-unreleased, 2026-06-30). Operator consequence: P1 type/security fix (sweeper:risk-security-boundary). Untrusted tool_call.id values were interpolated directly into file paths (f”{storage_dir}/{tool_use_id}.txt”), so an ID like ../../etc/cron.d/x could write outside the storage dir; shell quoting did not stop path traversal. New _safe_result_filename() in tools/tool_result_storage.py collapses unsafe chars, strips leading/trailing dots, and hashes on normalization. Operators running Hermes with untrusted or model-driven tool loops should re-audit and pull main (merge SHA 0ea3861) or wait for the next tag; this is a sandbox-escape-class boundary fix, not yet in v2026.6.19. Full receipted detail lives in harvest/watchlist.md.
Receipt
Finding metadata
Run: 2026-07-01-weekly-digest-2026-06-24_2026-07-01-frontier-v0
Finding ID: 2026-07-01-hermes-agent-path-traversal-fix-model-supplied-tool-call-ids-could-es
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact