# Keeping Fuzzers on Duty: Repairing Fuzzing Build Breakages in Continuous Open-Source Fuzzing

DevFeed: [Keeping Fuzzers on Duty: Repairing Fuzzing Build Breakages in Continuous Open-Source Fuzzing](<https://devfeed.tech/articles/keeping-fuzzers-on-duty-repairing-fuzzing-build-breakages-in-continuous-open-source-fuzzing-118075.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.06358>)

Author: Zhuang Zhao, Jiongchi Yu, Yao Zhang, Dongge Liu, Qiang Hu, Xiaohong Li, Yang Liu

Published: 2026-11-05T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [patches](<https://devfeed.tech/topics/patches.md>), [builds](<https://devfeed.tech/topics/builds.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [build](<https://devfeed.tech/tags/build.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [repair](<https://devfeed.tech/tags/repair.md>), [security-testing](<https://devfeed.tech/tags/security-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

FuzzMedic repairs OSS-Fuzz build breakages through evidence-guided diagnosis across project and fuzzing-infrastructure artifacts. It tracks workspace changes and build feedback in a repair-state graph, using branching and rollback to recover from unproductive repair paths. Candidate patches must restore executable fuzz targets, not just silence build failures. On 128 reproducible failures drawn from 1,820 real-world failures, it achieved a 48.44% repair rate and outperformed three program-repair baselines. In real-world use, 29 patches were merged upstream or into OSS-Fuzz, including fixes for three failures unresolved for over a year and two that had never built successfully.

## Source excerpt

arXiv:2611.06358v1 Announce Type: new Abstract: Continuous fuzzing platforms such as OSS-Fuzz provide sustained security testing for open-source projects, but long-term build breakages reduce security coverage and waste infrastructure resources. In OSS-Fuzz, around 20% of integrated projects remain in build-failure states, leaving their fuzzers off duty. These failures expose a maintenance gap between platform maintainers, who lack project-specific context, and project maintainers, who often lack fuzzing and infrastructure expertise. Existing program-repair techniques cannot be directly applied because fuzz build breakages span evolving project and infrastructure artifacts and require repeated infrastructure-aware diagnosis. We present FuzzMedic, an automated agent for fuzz build repair. FuzzMedic performs evidence-guided diagnosis across project and fuzzing-infrastructure artifacts. It explores repairs over a repair-state graph (RSG) that records the evolving workspace and build feedback. Branching and rollback enable FuzzMedic to recover from unproductive repair paths during long-horizon debugging. Candidate patches are validated to restore executable fuzz targets rather than merely suppress build failures. We evaluate FuzzMedic on 128 reproducible OSS-Fuzz build failures extracted from 1,820 real-world failures. FuzzMedic achieves a 48.44% repair rate and outperforms three representative program-repair baselines. In real-world use, it produces 29 patches merged into upstream or OSS-Fuzz main branches, including repairs for three failures that had remained unresolved for more than one year and two cases that had never built successfully.