PoCEvolve: Generating Proof-of-Concept Exploits from Security Patches with Vulnerability-Aware Prompt Evolution

· Source: cs.SE updates on arXiv.org · Field: Technology & Digital — Cybersecurity & Data Privacy, Artificial Intelligence & Machine Learning, Software Development & Engineering · Depth: Expert, short

Summary

PoCEvolve is a novel framework designed to generate Proof-of-Concept (PoC) exploits directly from vulnerability-fixing commits, addressing the critical delay between patch release and detailed vulnerability report availability. This gap leaves defenders exposed while attackers can reverse-engineer patches. PoCEvolve employs a vulnerability-aware prompt evolution mechanism that learns from unsuccessful generation attempts by assessing the usefulness of vulnerability-related context, including inferred vulnerable APIs and code-coverage information. Evaluated on SecBench.VFC.js, PoCEvolve achieved a PoC generation success rate of 58.4%, representing a 20.7% relative improvement over the state-of-the-art PoCGen and a 200.0% improvement over an LLM baseline with GPT-4o-mini. Using the Qwen3.7-Plus model, its success rate further increased to 85.3%. Even when detailed vulnerability reports are available, PoCEvolve reached a 71.7% success rate, surpassing PoCGen by 11.1%.

Key takeaway

For AI Security Engineers assessing new vulnerabilities, PoCEvolve offers a critical tool to generate Proof-of-Concept exploits directly from public security patches. This allows you to proactively understand exploitability and prioritize remediation efforts even before detailed vulnerability reports are released. You can validate fixes and enhance your defensive posture by utilizing this automated PoC generation, significantly reducing your window of exposure.

Key insights

PoCEvolve generates PoC exploits from security patches using vulnerability-aware prompt evolution, closing a critical defense gap.

Principles

Method

PoCEvolve synthesizes PoC exploits from vulnerability-fixing commits. It assesses vulnerable APIs and code-coverage to evolve prompts, learning from failures to guide LLMs.

In practice

Topics

Best for: Research Scientist, CTO, VP of Engineering/Data, AI Scientist, AI Security Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.SE updates on arXiv.org.