Fetching from the wire…
Public story · 2026-08-03 · high
It automates the data-flow, crash-semantics, and commit-history work engineers do by hand.
Why now: The paper entered the August 3, 2026 research corpus alongside AuditCoder's opposite finding on the same trace-versus-accuracy tradeoff.
AgenticRepair patched 73% of SEC-Bench's 300 real-world vulnerabilities, beating the strongest baseline by 29 points, per a new paper posted to arXiv.
The gap between general bug repair and vulnerability repair is the forensic work security teams already do by hand. They trace data flow across files, read crash semantics, and dig through commit history before writing a fix. Automating that reconstruction, not the patch itself, pushed the success rate to 73%.
Three specialized subagents each build one piece of that context. One maps cross-file data-flow and memory-operation structure. A second reconstructs runtime crash semantics and memory origins. The commit history showing how the fragile pattern got introduced comes from the third. A fourth subagent holds all three in memory and synthesizes the patch, instead of guessing from the vulnerable line alone.
Ablations in the paper show the three context types are complementary rather than redundant: dropping any one weakens the result.
A related paper, AuditCoder, tested the opposite bet on a different benchmark. Forcing a repair agent to output an explainable construction trace cost it 7.5 to 8.5 points of pass@1. AgenticRepair spends similar effort up front and gains accuracy instead of losing it.
The paper doesn't say what's failing in the remaining 27%, or whether the three-facet approach holds up outside SEC-Bench's instance set.
Each link below shares sources, entities, or timing with this story.
A proposed provenance gate cut unauthorized high-risk actions to zero after the attack itself hit a 1.000 success rate in tests.
A new checkpoint system saves an agent's memory and its environment together, so a failed attempt feeds the next try instead of getting discarded.
Sandbox memory in the test suite peaks at 28 GB a session, and latency across components swings up to 32x within the same app.
Comments explaining why a rule exists cut instruction bloat by 99.3%, per an analysis of 247,694 instruction lifetimes across 1,867 repositories.
The errors trace back to how the benchmark pairs pull requests with GitHub issues, not just to model quality.
The technique filters terminal output an agent reads one line of, and resolution rates held steady on 50 SWE-bench Lite tasks.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.