Nothing open on GitHub. Fix merged in #109509 on 13 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #109509. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #109509. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a security concern where state.db (and its WAL sidecars) are created with the process umask default (0644) rather than the intended restrictive 0600 permissions. The parent directory's 0700 mode is currently the only access control in place.
Open issues0
Open PRs0
Fixes on record
-
#109509 security: state.db, snapshots and memory locks are owner-only regardless of umask (salvage #102878 + #59716, goose#11613)
files:
contributors/emails/hermes-fleet-fix@localhost,hermes_cli/backup.py,hermes_state.py,tests/hermes_cli/test_backup_stability.py,tests/test_hermes_state.py,tests/tools/test_async_delegation.py,tests/tools/test_memory_tool.py,tools/async_delegation.py,tools/memory_tool_store.py
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
Closed issues · 1
- Closed#59706state.db is created 0644 (process umask), not 0600 -- the 0700 parent dir is its only protection
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.50: 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
- Subsystem
- agent
- Merged PRs
- #109509
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 13 Sep 2026