Bug: 141203588

Clone this repo:
  1. 83853d5 Upgrade oss-fuzz to fd15c6d57aa13667af2521daf6167a2d8cd2ecb7 am: ebda00b748 by Elliott Hughes · 3 months ago master
  2. ebda00b Upgrade oss-fuzz to fd15c6d57aa13667af2521daf6167a2d8cd2ecb7 by Elliott Hughes · 3 months ago android-s-v2-preview-1 android-s-v2-beta-2 android-s-v2-preview-2
  3. fd15c6d Add XNU (SockFuzzer) (#6583) by Ned Williamson · 3 months ago
  4. 2f03831 nDPI: add some missing (optional) dependencies (#6581) by Ivan Nardi · 3 months ago
  5. 0c5679c Run multiple jobs/workers by setting env vars (#5924) by Federico Maggi · 3 months ago

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.

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.

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.

Currently, OSS-Fuzz supports C/C++, Rust, Go, Python and Java/JVM code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.


OSS-Fuzz process diagram


Read our detailed documentation to learn how to use OSS-Fuzz.


As of June 2021, OSS-Fuzz has found over 30,000 bugs in 500 open source projects.

Blog posts