- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
A new attack is introduced as a "stepping-stone" attack, where the issue report is converted into a plan for the following agent to execute.
Critical strengths
Soundness The problem raised is an important security issue; an intermediary agent may forward communication to the following workflow if it appears to be its output. This needs to be addressed.
Presentation The architecture diagram in Figure 1 explains what this paper intends to do.
Significance The problem highlighted is vital in an agentic system with complex goals. Authors have tried to demonstrate it with a simple system implementation.
Critical weaknesses
In the SWE process, an external issue report is validated and tested for confirmation of the issue. Only when the issue is confirmed is it forwarded to the implementation team. The idea has a process flaw. Nevertheless, assuming adversarial interception at this stage, an intermediary agent is assigned a role to carry out, with clearly specified inputs and outputs. The issue report and plan will clearly have different formats and layouts. This will clearly depend on how well its role boundaries are written, whether it simply forwards it or plans it.
Soundness
- Does not follow SWE process of "issue life-cycle"?
- To provide a legitimate plan by an adversary, it should have knowledge of the architecture and tools within the system. For an intermediary agent to forward a plan, the plan should conform to the system's architectural implementation.
Presentation While figure 1 gives high level system setup with two agents, it is not clear what is "Bypass plan", "Host plan", and "Callback risk: YES" in table 1. Also, what setups are being used in the "planning" and "auditing" experiments? Table 2 has a lot of observations but is not referred and explained in the paper. I am assuming it might be trying to show that authors lauched attack successfully but I do not understand what each column signify
Significance Without implementing the full issue-report-repair process, it is difficult to demonstrate the significance of this software-engineering approach. It includes [issue report -> issue validation -> issue accepted -> issue repair design and implementation, and so on].
Questions for authors
- Do you use only Figure 1 for all experiments?
- In Table 1, what are "Bypass plan", "Host plan", and "Callback risk: YES" in table 1? Also, what setups are being used in the "planning" and "auditing" experiments?
- How are you arriving at these numbers in Table 1 and 2?
Response to Reviewer Nda1
We sincerely thank Reviewer Nda1 for the supportive evaluation and insightful questions regarding real software engineering lifecycle coverage, architectural tool knowledge, and presentation clarity. In our revision (Sections 3.2, 4, 5.1–5.2, 6, Tables 2–3, Appendices A–C; artifacts at
https://anonymous.4open.science/r/iclr2027-code-6ED5/), we expanded our empirical evidence and clarified these boundaries directly.1. Process & Lifecycle Coverage Across Real Workflows (W1)
Real-world development spans diverse trackers, triage steps, coding agents, and automated code reviewers. In Section 6 and Table 2, we explicitly clarify the single-repo Experiment 1–2 scope while showing transfer across real engineering tools:
2. System Architecture, Tool Knowledge, & Defense Boundaries (W2)
We grounded architectural authority and scope limitations in Sections 3.2, 5.2, 6, and Appendix C:
security/approved_callback_hosts.jsonreferenced inREADME.mdreduces unauthorized host adoption from 23/25 to 0/25 (p=2.4×10−7), with 24/25 (R2) to 25/25 (R3) runs routing to the approved internal endpoint.acme/replenishment-service) and endpoint (GET /api/reports/daily), while Experiment 3 extends across 32 synthetic evaluation families (8 initial + 24 held-out across network, supply-chain, identity, storage) plus 4 dev families (Appendix C).3. Clarity & Presentation Improvements (Q1–Q3)
162literal-positive plans), and Docker harness is indexed in Appendix Table 31 andhttps://anonymous.4open.science/r/iclr2027-code-6ED5/.