WuppieFuzz
github.com
- Free plan
- Open source
- Windows
- macOS
- Linux
- API
- Self-hosted
What WuppieFuzz is
WuppieFuzz is a free, open-source REST API fuzzer that uses coverage-guided techniques built on LibAFL to look for possible errors and security flaws. It generates and mutates requests from an OpenAPI specification, so users need that API description to start. Testing modes include black-box, grey-box, and white-box, with support for authentication and input-validation testing. Authentication documentation covers Bearer, custom, cookie, OAuth, and Web Fuzzing Commons formats. The tool can produce endpoint coverage reports. Code coverage support is described for Java, JavaScript, and Python, though code coverage reporting is currently available only for JaCoCo. A Grafana dashboard can visualize request information from a fuzzing campaign. WuppieFuzz is self-hosted and available for Windows, macOS, and Linux under the Apache 2.0 license. TNO says fuzzing data is not shared with TNO or third parties. The maker describes the tool as suitable for a broad audience and for use in software development, supply-chain quality control, or penetration testing. API discovery is not supported.
Who it suits
WuppieFuzz suits developers and security teams that have an OpenAPI description and want to fuzz REST APIs in their own environment. It can also fit software development, supply-chain quality control, or penetration-testing work.
Good to know, and what to watch
- Supports black-box, grey-box, and white-box testing
- Tests authentication and input validation
- Self-hosted on Windows, macOS, and Linux
- Fuzzing data is not shared with TNO or third parties
- Requires an OpenAPI specification
- Does not provide API discovery
- Code coverage reports currently support only JaCoCo
Plans
Every plan and priceWuppieFuzz
WuppieFuzz Free
Open source
The verdict
WuppieFuzz offers several REST API testing modes and self-hosted deployment at no charge. Its reliance on OpenAPI specifications and the current JaCoCo reporting limit are important fit considerations.
What the maker publishes
- API specification
- It requires an OpenAPI specification to generate and mutate requests. source
- Audience and uses
- TNO describes the tool as intended for a broad audience and usable during software development, supply-chain quality control, or penetration testing. source
- Authentication
- Authentication documentation describes Bearer, custom, cookie, OAuth, and Web Fuzzing Commons formats. source
- Automated harness
- The tool automates creation of the HTTP fuzzing harness, reducing manual setup work. source
- Black-box fallback
- Black-box testing remains available without a coverage agent, but provides less detailed feedback than line coverage. source
- CLI and configuration
- The command-line interface accepts an OpenAPI file, and YAML configuration files can be combined with command-line flags, with flags taking precedence. source
- Code coverage
- The maker says code coverage is supported for Java, JavaScript, and Python, and that adding languages is possible. source
- Coverage agents
- The research describes coverage agents for Java, Python and JavaScript, with a modular design intended to allow more languages. source
- Coverage feedback
- Scheduling can use code coverage and endpoint coverage gathered through coverage agents. source
- Dashboard
- A Grafana dashboard can visualize and explore the database of request information from a fuzzing campaign. source
- Dashboard
- A Grafana dashboard is supplied to visualize and explore fuzzing results. source
- Developer prerequisites
- Building from source requires build-essential, pkg-config, CMake and Rust, with OpenSSL, SQLite and Z3 system-library options documented. source
- Docker
- The project documents building a Docker image and running it with a mounted fuzzing directory and host networking for local targets. source
- Documentation depth
- The repository includes a low-level tutorial, example configurations, coverage-agent instructions and generated Rust API documentation support. source
- Extensibility
- The project invites contributions such as new language coverage agents and mutation techniques. source
- Independent registry status
- The Dutch open-source registry marks the repository status as stable and lists Linux, macOS and Windows platforms. source
- Independent technical description
- An ETSI workshop presentation characterizes WuppieFuzz as an open-source, LibAFL-based coverage-guided REST API fuzzer using OpenAPI response conformance and endpoint coverage. source
- Install platforms
- The README points users to releases or Homebrew for macOS, Windows and Linux installation. source
- Latest repository release
- The GitHub repository page currently presents WuppieFuzz v1.8.0. source
- Licence
- WuppieFuzz is distributed under the Apache-2.0 licence. source
- License
- WuppieFuzz is available under the Apache 2.0 license. source
- Limit: black-box detail
- Without a coverage agent, testing can measure endpoint coverage but cannot provide the detail of line-coverage feedback. source
- Limit: result minimization
- The research paper identifies automated minimization of the request sequence and parameters causing a failure as future work. source
- Limit: specification dependency
- The research architecture requires an OpenAPI specification describing the system under test before fuzzing can start. source
Checked against the maker's pages on 15 Oct 2026.