Evidence · DiggingBeagle record
CrossPloit benchmark: agent PoC migration across old library versions
Original paper on validating known vulnerability PoCs in earlier historical versions omitted by advisory databases, and evaluating exploit migration agents.
- Published
- Nov 12, 2026
- Source role
- primary disclosure
Evidence record
Original paper on validating known vulnerability PoCs in earlier historical versions omitted by advisory databases, and evaluating exploit migration agents.
Claim-level citations (2)
- supportsCrossPloit used executable tests to show 149 older vulnerable releases omitted from advisory version ranges: The benchmark sampled known Python web-application CVEs, confirmed original exploits and then tested older releases that vulnerability databases did not identify as affected. Agents were asked to migrate PoCs when the old source, API or dependency structure made a direct replay ineffective. Researchers verified 149 older affected historical releases across 45 already-known CVEs; 22 reused the original PoC unchanged while 127 required migration. In selected agent evaluations, more than half of migration tasks succeeded when sufficient exploit and environment evidence was supplied.
CrossPloit paper, benchmark construction, 149 historical releases, 127 migration tasks and experimental results
- supportsCrossPloit used executable tests to show 149 older vulnerable releases omitted from advisory version ranges: These are missing vulnerable version ranges for previously known CVEs, not 149 previously unknown zero-days or 149 observed production compromises. Unresolved testing results must not be counted as unaffected versions. The consequential AI-security question is how automated exploit migration changes the reach of a known bug across unlisted software history.
Primary disclosure: results, scope and limitations