Cairn
NousResearch/hermes-agent

Block sensitive-path writes in managed-files API

Cluster 85387 · dashboard. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items address a security gap where write endpoints in the dashboard's managed-files API lacked guards against overwriting sensitive files such as .env and config.yaml. The work involves applying credential/sensitive-path protections consistently across both read and write routes.

Open issues1

  • Issue#85387[Security] Dashboard managed-files write endpoints can overwrite .env / config.yaml — read-side sensitive guard not applied to writes

Open PRs1

  • PR#85415fix(security): block writes to sensitive paths in managed-files API

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #125994 fix(dashboard): apply credential guards to every fs/git file route · superseded by another PR → #58724
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

Subsystem
dashboard
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/85387.json
cluster/85387.md