SecDome Logo SecDome
PATCH REPAIR // REMEDIATION
PATCH RIGOR BENCHMARK SPECIFICATION

FixBench Security Patch Remediation & Invariant Preservation

Evaluating whether automated security agent patches invalidate real exploit payloads while preserving complete functional test suites and introducing zero secondary vulnerabilities.

TARGET CORPUS

Python, Go, Java, Node.js, C/C++

DATASET SCALE

Verified CVE Remediation Topologies

VERIFICATION ORACLE

Dual-Gate (PoC Invalidation + Regressions)

EVALUATION TARGET

Exploit Invalidation / Zero Regressions

EVALUATION MOTIVATION

Core Research Problem

While general software engineering benchmarks evaluate generic bug fixing, vulnerability remediation is fundamentally adversarial. A security patch must satisfy three simultaneous criteria: it must neutralize the active exploit payload, cause zero regression on legitimate application unit tests, and avoid introducing subtle secondary security defects. FixBench formalizes these three criteria into an automated evaluation protocol.

01 // EVALUATED CAPABILITY

Exploit Vector Invalidation

The candidate patch must fundamentally disrupt the causal path of the reproducible PoC test case.

02 // EVALUATED CAPABILITY

Zero Functional Regression

The complete upstream unit test suite must pass without any behavioral drift or breaking API changes.

03 // EVALUATED CAPABILITY

Secondary Flaw Prevention

Automated AST and sanitizer audits ensure the patch does not introduce new type errors, denial-of-service, or injection bypasses.

04 // EVALUATED CAPABILITY

Minimal Patch Diff Footprint

Penalizes over-broad refactoring in favor of focused, maintainable, minimal invariant-preserving edits.

VERIFICATION PROTOCOL

Deterministic Execution Pipeline

Every evaluation task follows a structured, auditable lifecycle from ingestion to oracle confirmation.

01

Isolated Container Build

Vulnerable repository is compiled and booted inside an isolated container with baseline regression tests verified.

02

Candidate Patch Synthesis

Autonomous agent inspects vulnerability report and code context, synthesizing a candidate patch diff.

03

Dual-Oracle Automated Trial

Container applies patch: PoC exploit must fail, full regression test suite must pass, and static sanitizers confirm safety.

EVALUATION CRITERIA

Falsifiable Scoring Standards

SecDome enforces strict ground-truth verification standards. No speculative scoring or synthetic shortcuts.

CRITERION 01

Deterministic Exploit Disruption

Patch must cause the existing automated PoC script to fail cleanly without throwing unexpected crashes.

CRITERION 02

Regression Test Invariance

100% of the repository existing unit, integration, and end-to-end tests must execute successfully.

CRITERION 03

Structural Safety Audit

Post-patch AST analysis verifies no dangerous sinks, permissive typecasts, or swallowed exceptions were introduced.

CURRENT BENCHMARK STATUS & ROADMAP

Evaluation harness and dual-oracle specification finalized. Corpus containerization in progress; baseline comparative results will be released openly upon completion of verification campaigns.

OPEN SCIENCE PRINCIPLE

Reproducible & Auditable.

All SecDome benchmark specifications, task schemas, and evaluation protocols are maintained openly under Apache 2.0 / MIT. We invite external research groups to audit our task definitions and contribute reproducible evaluation environments.

BENCHMARK GOVERNANCE OPEN SPECIFICATION
SPECIFICATION: FixBench v1.0 Spec
REPOSITORY: github.com/secdome
PEER AUDIT: Open Access / RFC
LICENSE: Apache 2.0 / MIT