Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[LAUNCH-E M6, Medium] Restrict UPDATE_EPIC's next issue to the EPIC's own sub-issues

Open
  • Is something wrong?
#287 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github, python
Domain
backend, security

Research direction

Start with _verify_issue_selectable in src/autoforge/engine.py and compare its checks with the EPIC sub-issue admission rule. Read the “After UPDATE_EPIC” guidance in docs/agent-guides/github-safety.md and the disclosure in docs/security.md; update the named workflow and security documentation alongside the validation. Done means an unrelated open issue is refused, a verified EPIC sub-issue is accepted, fake-only tests pass, and the Known limitations entry is removed.

Written by the indexing model from the issue text.

Description

bug

Artifact: follow-up issue for audit finding M6 (Medium) of the LAUNCH-E security audit (#257, PR #279); disposition 'follow-up, disclosed in Known limitations until fixed' recorded by the maintainer on #257. This issue body is the authoritative copy. Audited commit: 388ecb3b9d6376f8914054cc06ea5e5caab164da (main); line numbers below are at that commit.

Parent: #255 · Audit: #257 · Audit PR: #279 · Severity: Medium · Related: accepted residual R2 (public-repository prompt injection), which this widens

Summary

In a sequential EPIC run, UPDATE_EPIC's agent proposes next_issue_url, and the controller accepts any open issue of the run's repository other than the EPIC and the current issue. It need not be an issue the EPIC references. On a public repository that can be an issue a stranger opened, so injected text can choose the next task, not only influence the current one. autoforge epic run already admits only the EPIC's own sub-issues.

Evidence (at 388ecb3)

  • src/autoforge/engine.py:6299-6362 (_verify_issue_selectable: repository, not-EPIC, not-current, exists, open).
  • docs/agent-guides/github-safety.md ("After UPDATE_EPIC"); disclosed in docs/security.md ("Prompt injection, and public repositories in particular").

Scope

  1. Restrict the next issue to one the EPIC references as a native sub-issue (and, if kept, an explicitly listed task-list reference), verified on GitHub, matching the epic run admission rule; refuse anything else with a clear BLOCKED reason.
  2. Update workflow.md, github-safety.md and docs/security.md, and remove the Known-limitations entry once fixed.

Acceptance criteria

  • UPDATE_EPIC with a next_issue_url that is open but not a sub-issue of the EPIC is refused; a sub-issue is accepted.
  • Tests use fakes only; make check passes.
Dominant language
Python
Stars
0
Forks
0
Avg merge
6h
Merged PRs (30d)
78

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from iceboundrock/AutoForge

All issues in iceboundrock/AutoForge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.