Cairn

Cron script path validation and security fixes

NousResearch/hermes-agent · cluster 59599 · cron

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These issues and pull requests address path handling in cron job scripts, including rejection of absolute paths, path traversal guards, relative path resolution, and clearer error messaging.

Open issues1

  • Issue#59599cronjob create rejects absolute script paths without clear error guidance

Open PRs3

  • PR#38695fix(tools): use display_hermes_home() in cron script validation error messages
  • PR#59644fix(cron): clear error when cronjob create rejects absolute script paths (#59599)
  • PR#60475fix(cron): resolve relative script paths relative to job workdir instead of cwd (#59599)
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.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
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/59599.json
cluster/59599.md