google /oss-fuzz
OSS-Fuzz - continuous fuzzing for open source software.
★ 12,957⑂ 3,000👁 244⑃ 13,814● 2,626▤ 0
+3
Daily
12,957
stars
3,000
forks
244
watchers
13,814
prs
2,626
issues
0
releases
README
OSS-Fuzz: Continuous Fuzzing for Open Source Software [Fuzz testing] is a well-known technique for uncovering programming errors in software. Many of these detectable errors, like [buffer overflow], can have serious security implications. Google has found [thousands] of security vulnerabilities and stability bugs by deploying [guided in-process fuzzing of Chrome components], and we now want to share that service with the open source community. [Fuzz testing]: https://en.wikipedia.org/wiki/Fuzz_testing [buffer overflow]: https://en.wikipedia.org/wiki/Buffer_overflow [thousands]: https://issues.chromium.org/issues?q=label:Stability-LibFuzzer%20-status:Duplicate,WontFix [guided in-process fuzzing of Chrome components]: https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html In cooperation with the [Core Infrastructure Initiative] and the [OpenSSF], OSS-Fuzz aims to make common open source software more secure and stable by combining modern fuzzing techniques with scalable, distributed execution. Projects that do not qualify for OSS-Fuzz (e.g. closed source) can run their own instances of [ClusterFuzz] or [ClusterFuzzLite]. [Core Infrastructure Initiative]: https://www.coreinfrastructure.org/ [OpenSSF]: https://www.openssf.org/ We support the [libFuzzer], [AFL++], and [Honggfuzz] fuzzing engines in combination with [Sanitizers], as well as [ClusterFuzz], a distributed fuzzer execution environment and reporting tool. [libFuzzer]: https://llvm.org/docs/LibFuzzer.html [AFL++]: https://github.com/AFLplusplus/AFLplusplus [Honggfuzz]: https://github.com/google/honggfuzz [Sanitizers]: https://github.com/google/sanitizers [ClusterFuzz]: https://github.com/google/clusterfuzz [ClusterFuzzLite]: https://google.github.io/clusterfuzzlite/ Currently, OSS-Fuzz supports C/C++, Rust, Go, Python, Java/JVM, JavaScript and Lua code. Other languages supported by [LLVM] may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds. [LLVM]: https://llvm.org Overview !OSS-Fuzz process diagram Documentation Read our [detailed documentation] to learn how to use OSS-Fuzz. [detailed documentation]: https://google.github.io/oss-fuzz Trophies As of May 2025, OSS-Fuzz has helped identify and fix over 13,000 vulnerabilities and 50,000 bugs across [1,000] projects. [1,000]: https://github.com/google/oss-fuzz/tree/master/projects Blog posts 2024-11-20 - [Leveling Up Fuzzing: Finding more vulnerabilities with AI] 2023-08-16 - [AI-Powered Fuzzing: Breaking the Bug Hunting Barrier] 2023-02-01 - [Taking the next step: OSS-Fuzz in 2023] 2022-09-08 - [Fuzzing beyond memory corruption: Finding broader classes of vulnerabilities automatically] 2021-12-16 - [Improving OSS-Fuzz and Jazzer to catch Log4Shell] 2021-03-10 - [Fuzzing Java in OSS-Fuzz] 2020-12-07 - [Improving open source security during the Google summer internship program] 2020-10-09 - [Fuzzing internships for Open Source Software] 2018-11-06 - [A New Chapter for OSS-Fuzz] 2017
Top issues
#10090CIFuzz and GitHub code scanning alerts26 comments · 2023-04-14#11398idea: treat a major coverage drop an issue!21 comments · 2023-12-22#13289Build failures aren't reported by OSS-Fuzz16 comments · 2025-05-07#8324Support Fuzzing JavaScript with Jazzer.js16 comments · 2022-08-23#12508Issue tracker migration14 comments · 2024-09-17#11143Broken introspector report (`pandas` project)14 comments · 2023-10-20#15009With new oss-fuzz Ubuntu 24.04 baseline, automatically allocated (stack) variables are reported as used uninitialized12 comments · 2026-02-22#14780CIFuzz of libsrtp fails bad_build_check with "Invalid argument: --"12 comments · 2026-01-10
Discussions
#15994GPU codecs: host-side targets now; GPU-capable runners ever?0 comments · 2026-08-13#15403zip-rs needs configuration update3 comments · 2026-04-23#14219Is it possible to fuzz Rust repos with multiple `fuzz` folders?0 comments · 2025-10-31#14061Open Source - Open Arms0 comments · 2025-09-25#14044Guidelines for interpreting fuzzer statistics2 comments · 2025-09-22#13148How to Access Execution Time & Crash Count Data for OSS-Fuzz Projects?3 comments · 2025-03-18#13005When fuzzing C or C++ projects, is it necessary to instrument the dependent third-party static libraries?0 comments · 2025-02-04#12934Cannot build after switching to fmtlib0 comments · 2025-01-13