AI-powered workflow automation and AI Agents for AppSec, Fuzzing & Offensive Security
Overview β’ Features β’ Installation β’ Quickstart β’ AI Demo β’ Contributing β’ Roadmap
FuzzForge helps security researchers and engineers automate application security and offensive security workflows with the power of AI and fuzzing frameworks.
- Orchestrate static & dynamic analysis
- Automate vulnerability research
- Scale AppSec testing with AI agents
- Build, share & reuse workflows across teams
FuzzForge is open source, built to empower security teams, researchers, and the community.
π§ FuzzForge is under active development. Expect breaking changes.
If you find FuzzForge useful, please star the repo to support development π
- π€ AI Agents for Security β Specialized agents for AppSec, reversing, and fuzzing
- π Workflow Automation β Define & execute AppSec workflows as code
- π Vulnerability Research at Scale β Rediscover 1-days & find 0-days with automation
- π Fuzzer Integration β AFL, Honggfuzz, AFLnet, StateAFL & more
- π Community Marketplace β Share workflows, corpora, PoCs, and modules
- π Enterprise Ready β Team/Corp cloud tiers for scaling offensive security
Python 3.11+ Python 3.11 or higher is required.
uv Package Manager
curl -LsSf https://astral.sh/uv/install.sh | shDocker For containerized workflows, see the Docker Installation Guide.
After installing the requirements, install the FuzzForge CLI:
# Clone the repository
git clone https://github.com/fuzzinglabs/fuzzforge_ai.git
cd fuzzforge_ai
# Install CLI with uv (from the root directory)
uv tool install --python python3.12 .Run your first workflow :
# 1. Clone the repo
git clone https://github.com/fuzzinglabs/fuzzforge.git
cd fuzzforge
# 2. Build & run with Docker
# Set registry host for your OS (local registry is mandatory)
# macOS/Windows (Docker Desktop):
export REGISTRY_HOST=host.docker.internal
# Linux (default):
# export REGISTRY_HOST=localhost
docker compose up -dThe first launch can take 5-10 minutes due to Docker image building - a good time for a coffee break β
# 3. Run your first workflow
cd test_projects/vulnerable_app/ # Go into the test directory
fuzzforge init # Init a fuzzforge project
ff workflow run security_assessment . # Start a workflow (you can also use ff command)Setting up and running security workflows through the interface
π More installation options in the Documentation.
AI agents automatically analyzing code and providing security insights
- π Website
- π Documentation
- π¬ Community Discord
- π FuzzingLabs Academy
We welcome contributions from the community!
There are many ways to help:
- Report bugs by opening an issue
- Suggest new features or improvements
- Submit pull requests with fixes or enhancements
- Share workflows, corpora, or modules with the community
See our Contributing Guide for details.
Planned features and improvements:
- π¦ Public workflow & module marketplace
- π€ New specialized AI agents (Rust, Go, Android, Automotive)
- π Expanded fuzzer integrations (LibFuzzer, Jazzer, more network fuzzers)
- βοΈ Multi-tenant SaaS platform with team collaboration
- π Advanced reporting & analytics
π Follow updates in the GitHub issues and Discord.
FuzzForge is released under the Business Source License (BSL) 1.1, with an automatic fallback to Apache 2.0 after 4 years.
See LICENSE and LICENSE-APACHE for details.


