Cron job prompt injection and privilege security fixes
Cluster 8886 · cron. Data as of
1 open item. Fix merged in #31947 on 25 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #31947. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #31947, then check whether your report is the one still open.
Read #31947Pick up a Lab taskThese issues and pull requests address security vulnerabilities in cron job execution, specifically around prompt scanning that could be bypassed via skill content, privilege hardening, and related approval and toolset controls.
Open issues1
- Issue#8886[Bug]: Cron Job Full Privilege Execution with Trivially Bypassable Prompt Scanning
Open PRs0
Fixes on record
-
#31947 fix(cron): layer agent.disabled_toolsets onto cron baseline (#25752, salvage)
files:
cron/scheduler.py,scripts/release.py,tests/cron/test_scheduler.py
1 PR closed without merging
From the close comments: closed without comment 1
- #9124 fix: harden cron job privilege and prompt scanning · closed without comment
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.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
- cron
- Merged PRs
- #31947
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 May 2026