DeepAudit - Your AI Security Audit Team, Making Vulnerability Discovery Accessible

March 25, 2026 · View on GitHub

DeepAudit Logo

Version License: AGPL-3.0 React TypeScript FastAPI Python Ask DeepWiki

Stars Forks

lintsinghua%2FDeepAudit | Trendshift

简体中文 | English

DeepAudit Demo

Screenshots

Agent Audit Entry

Agent Audit Entry

Quick access to Multi-Agent deep audit from the homepage

Audit Flow Logs

Audit Flow Logs
Real-time visibility into agent reasoning and execution
Smart Dashboard

Smart Dashboard
Understand the overall security posture of a project at a glance
Instant Analysis

Instant Analysis
Paste code or upload files and get results in seconds
Project Management

Project Management
Import from GitHub/GitLab/Gitea and manage multiple projects together

Professional Reports

Audit Report

One-click export to PDF / Markdown / JSON (the screenshot shows quick mode, not an Agent-mode report)

View the full Agent audit report example


CVE Vulnerability Discoveries

DeepAudit has successfully discovered and obtained 49 CVE IDs and 6 GHSA security advisories

Across 17 well-known open-source projects

OpenClaw vulnerability research results

The internal preview version of DeepAudit performed a deep security audit on the OpenClaw project and has so far discovered 6 security vulnerabilities, all of which were officially confirmed and published as security advisories (GHSA). The issues cover command injection, signature verification bypass, remote code execution, credential exposure, resource exhaustion, and information disclosure, including multiple high-severity findings. More vulnerabilities are still being researched.

GHSA IDProjectPopularityVulnerability TypeSeverity
GHSA-g353-mgv3-8pcjOpenClawStarsSignature Verification Bypass8.6
GHSA-99qw-6mr3-36qrOpenClawStarsCode Execution8.5
GHSA-7h7g-x2px-94hjOpenClawStarsCredential Exposure6.9
GHSA-g2f6-pwvx-r275OpenClawStarsCommand InjectionMedium
GHSA-jq3f-vjww-8rq7OpenClawStarsResource ExhaustionHigh
GHSA-xwcj-hwhf-h378OpenClawStarsInformation DisclosureMedium
CVE IDProjectPopularityVulnerability TypeCVSS
CVE-2026-1884Zentao PMSStarsSSRF5.1
CVE-2025-13789Zentao PMSStarsSSRF5.3
CVE-2025-13787Zentao PMSStarsPrivilege Escalation9.1
CVE-2025-64428DataeaseStarsJNDI Injection9.8
CVE-2025-13246ModulithshopStarsSQL Injection6.3
CVE-2025-64163DataeaseStarsSSRF9.8
CVE-2025-64164DataeaseStarsJNDI Injection9.8
CVE-2025-11581PowerJobStarsPrivilege Escalation7.5
CVE-2025-11580PowerJobStarsPrivilege Escalation5.3
CVE-2025-10771JimureportStarsDeserialization9.8
CVE-2025-10770JimureportStarsDeserialization6.5
CVE-2025-10769H2o-3StarsDeserialization9.8
CVE-2025-10768H2o-3StarsDeserialization9.8
CVE-2025-58045DataeaseStarsJNDI Injection9.8
CVE-2025-10423Newbee-mallStarsGuessable Captcha3.7
CVE-2025-10422Newbee-mallStarsPrivilege Escalation4.3
CVE-2025-9835MallStarsPrivilege Escalation4.3
CVE-2025-9737O2oaStarsXSS5.4
CVE-2025-9736O2oaStarsXSS5.4
CVE-2025-9735O2oaStarsXSS5.4
CVE-2025-9734O2oaStarsXSS5.4
CVE-2025-9719O2oaStarsXSS5.4
CVE-2025-9718O2oaStarsXSS5.4
CVE-2025-9717O2oaStarsXSS5.4
CVE-2025-9716O2oaStarsXSS5.4
CVE-2025-9715O2oaStarsXSS5.4
CVE-2025-9683O2oaStarsXSS5.4
CVE-2025-9682O2oaStarsXSS5.4
CVE-2025-9681O2oaStarsXSS5.4
CVE-2025-9680O2oaStarsXSS5.4
CVE-2025-9659O2oaStarsXSS5.4
CVE-2025-9658O2oaStarsXSS5.4
CVE-2025-9657O2oaStarsXSS5.4
CVE-2025-9655O2oaStarsXSS5.4
CVE-2025-9646O2oaStarsXSS5.4
CVE-2025-9602RockOAStarsDatabase Backdoor6.5
CVE-2025-9514MallStarsPrivilege Escalation3.7
CVE-2025-9264Xxl-jobStarsPrivilege Escalation5.4
CVE-2025-9263Xxl-jobStarsPrivilege Escalation4.3
CVE-2025-9241EladminStarsCSV/XLSX Injection7.5
CVE-2025-9240EladminStarsSensitive Information Disclosure4.3
CVE-2025-9239EladminStarsHardcoded Credentials3.7
CVE-2025-8974LitemallStarsHardcoded Credentials9.8
CVE-2025-8852Wukong CRMStarsSensitive Information Disclosure4.3
CVE-2025-8840JshERPStarsPrivilege Escalation5.4
CVE-2025-8839JshERPStarsPrivilege Escalation8.8
CVE-2025-8764LitemallStarsXSS5.4
CVE-2025-8753LitemallStarsArbitrary File Deletion5.4
CVE-2025-8708White-JotterStarsDeserialization7.5

View the full CVE list

The vulnerabilities above were discovered with DeepAudit by DeepAudit team members @lintsinghua and @ez-lbz.

If you discover vulnerabilities using DeepAudit, you are welcome to leave feedback in Issues. Your contributions will greatly enrich this vulnerability list.


Overview

DeepAudit is a next-generation code security auditing platform built on a Multi-Agent collaborative architecture. It is not just a static scanner. Instead, it simulates the reasoning model of security experts through autonomous collaboration among multiple intelligent agents (Orchestrator, Recon, Analysis, Verification) to achieve deep code understanding, vulnerability discovery, and automated sandboxed PoC verification.

We are committed to solving three major pain points of traditional SAST tools:

  • High false-positive rates: lack of semantic understanding leads to large amounts of noisy findings and wasted review effort
  • Business-logic blind spots: inability to understand cross-file calls and complex logic flows
  • Lack of verification: no way to determine whether a vulnerability is actually exploitable

Users only need to import a project, and DeepAudit automatically starts the workflow: identify the technology stack, analyze potential risks, generate exploit scripts, verify them in a sandbox, and then produce a professional audit report.

Core philosophy: Let AI attack like a hacker and defend like an expert.

Why Choose DeepAudit?

Traditional Audit Pain PointsDeepAudit Solutions
Low manual audit efficiency
Cannot keep up with CI/CD iteration speed and slows down releases
Multi-Agent autonomous auditing
AI automatically orchestrates auditing strategies and runs them around the clock
Too many false positives
Lack of semantic understanding means a lot of time is wasted cleaning noisy findings
RAG knowledge enhancement
Combines code semantics with project context to significantly reduce false positives
Data privacy concerns
Worried about core source code leaking to cloud AI services and failing compliance requirements
Ollama local deployment support
Data stays inside your environment and supports local models such as Llama3 and DeepSeek
Cannot confirm real exploitability
Too many findings in outsourced projects and no clear way to know which are real
Sandboxed PoC verification
Automatically generates and runs attack scripts to confirm real impact

System Architecture

Architecture Diagram

DeepAudit uses a microservice architecture driven by a Multi-Agent engine at its core.

DeepAudit Architecture Diagram

Audit Workflow

StepPhaseResponsible AgentMain Actions
1Strategy PlanningOrchestratorReceives the audit task, analyzes the project type, creates an audit plan, and dispatches tasks to sub-agents
2Information GatheringRecon AgentScans the project structure, identifies frameworks, libraries, and APIs, and extracts entry points
3Vulnerability DiscoveryAnalysis AgentCombines RAG knowledge and AST analysis to deeply inspect the code and find potential vulnerabilities
4PoC VerificationVerification Agent(Critical) Writes PoC scripts and executes them in a Docker sandbox, with self-correction and retries on failure
5Report GenerationOrchestratorAggregates all findings, removes false positives disproven by verification, and generates the final report

Project Structure

DeepAudit/
├── backend/                        # Python FastAPI backend
│   ├── app/
│   │   ├── agents/                 # Multi-Agent core logic
│   │   │   ├── orchestrator.py     # Command center: task orchestration
│   │   │   ├── recon.py            # Reconnaissance: asset identification
│   │   │   ├── analysis.py         # Analyst: vulnerability discovery
│   │   │   └── verification.py     # Verifier: sandbox PoC
│   │   ├── core/                   # Core configuration and sandbox interfaces
│   │   ├── models/                 # Database models
│   │   └── services/               # RAG and LLM service wrappers
│   └── tests/                      # Unit tests
├── frontend/                       # React + TypeScript frontend
│   └── src/
│       ├── components/             # UI component library
│       ├── pages/                  # Page routes
│       └── stores/                 # Zustand state management
├── docker/                         # Docker deployment configuration
│   ├── sandbox/                    # Secure sandbox image build
│   └── postgres/                   # Database initialization
└── docs/                           # Detailed documentation

Quick Start

Use the prebuilt Docker images. You do not need to clone the repository:

curl -fsSL https://raw.githubusercontent.com/lintsinghua/DeepAudit/v3.0.0/docker-compose.prod.yml | docker compose -f - up -d

China-Accelerated Deployment

Use the Nanjing University mirror site to accelerate pulling Docker images by replacing ghcr.io with ghcr.nju.edu.cn:

# China-accelerated version using the Nanjing University GHCR mirror
curl -fsSL https://raw.githubusercontent.com/lintsinghua/DeepAudit/v3.0.0/docker-compose.prod.cn.yml | docker compose -f - up -d
Manually pull images if needed (click to expand)
# Frontend image
docker pull ghcr.nju.edu.cn/lintsinghua/deepaudit-frontend:latest

# Backend image
docker pull ghcr.nju.edu.cn/lintsinghua/deepaudit-backend:latest

# Sandbox image
docker pull ghcr.nju.edu.cn/lintsinghua/deepaudit-sandbox:latest

Mirror support is provided by the Nanjing University Open Source Mirror Station.

Configure Docker registry mirrors (optional, for even faster image pulling) (click to expand)

If image pulling is still slow, you can configure Docker registry mirrors by editing the Docker daemon configuration.

Linux / macOS: edit /etc/docker/daemon.json

Windows: right-click the Docker Desktop tray icon -> Settings -> Docker Engine

{
  "registry-mirrors": [
    "https://docker.1ms.run",
    "https://dockerproxy.com",
    "https://hub.rat.dev"
  ]
}

Restart Docker after saving:

# Linux
sudo systemctl restart docker

# macOS / Windows
# Restart Docker Desktop

Started successfully? Open http://localhost:3000 to begin.


Option 2: Clone and Deploy

Suitable if you need custom configuration or want to develop on top of the project:

# 1. Clone the project
git clone https://github.com/lintsinghua/DeepAudit.git && cd DeepAudit

# 2. Configure environment variables
cp backend/env.example backend/.env
# Edit backend/.env and fill in your LLM API key

# 3. Start everything
docker compose up -d

The first startup will automatically build the sandbox image and may take a few minutes.


Source Development Guide

Suitable for developers doing secondary development and debugging.

Requirements

  • Python 3.11+
  • Node.js 20+
  • PostgreSQL 15+
  • Docker (for the sandbox)

1. Start the database manually

docker compose up -d redis db adminer

2. Start the backend

cd backend
# Configure environment variables
cp env.example .env

# Use uv to manage the environment (recommended)
uv sync
source .venv/bin/activate

# Start the API service
uvicorn app.main:app --reload

3. Start the frontend

cd frontend
# Configure environment variables
cp .env.example .env

pnpm install
pnpm dev

4. Sandbox environment

In development mode, you need to pull the sandbox image locally:

# Standard pull
docker pull ghcr.io/lintsinghua/deepaudit-sandbox:latest

# China-accelerated pull (Nanjing University mirror)
docker pull ghcr.nju.edu.cn/lintsinghua/deepaudit-sandbox:latest

Multi-Agent Intelligent Audit

Supported Vulnerability Types

Vulnerability TypeDescription
sql_injectionSQL injection
xssCross-site scripting
command_injectionCommand injection
path_traversalPath traversal
ssrfServer-side request forgery
xxeXML external entity injection
Vulnerability TypeDescription
insecure_deserializationInsecure deserialization
hardcoded_secretHardcoded secrets
weak_cryptoWeak cryptography
authentication_bypassAuthentication bypass
authorization_bypassAuthorization bypass
idorInsecure direct object reference

For detailed documentation, see Agent Audit Guide.


Supported LLM Platforms

International Platforms

OpenAI GPT-4o / GPT-4
Claude 3.5 Sonnet / Opus
Google Gemini Pro
DeepSeek V3

China Platforms

Tongyi Qwen
Zhipu GLM-4
Moonshot Kimi
Wenxin Yiyan / MiniMax / Doubao

Local Deployment

Ollama
Llama3 / Qwen2.5 / CodeLlama
DeepSeek-Coder / Codestral
Your code stays on-premises

Supports API relay/proxy endpoints to address network access issues. See LLM Platform Support for details.


Feature Matrix

FeatureDescriptionMode
Agent deep auditMulti-Agent collaboration with autonomous audit strategy orchestrationAgent
RAG knowledge enhancementCode semantic understanding with CWE/CVE knowledge-base retrievalAgent
Sandbox PoC verificationDocker-isolated execution to verify exploitabilityAgent
Project managementGitHub/GitLab/Gitea import, ZIP upload, 10+ language supportGeneral
Instant analysisAnalyze code snippets in seconds by pasting them directlyGeneral
Five-dimensional inspectionBug / Security / Performance / Style / MaintainabilityGeneral
What-Why-HowPrecise issue location, root-cause explanation, and remediation suggestionsGeneral
Audit rulesBuilt-in OWASP Top 10 with support for custom rule setsGeneral
Prompt templatesVisual management with bilingual supportGeneral
Report exportOne-click export to PDF / Markdown / JSONGeneral
Runtime configurationConfigure LLM settings in the browser without restarting servicesGeneral

Roadmap

We are continuing to evolve the platform with support for more languages and stronger agent capabilities.

  • Basic static analysis with Semgrep integration
  • RAG knowledge base and Docker security sandbox support
  • Multi-Agent collaborative architecture (current)
  • Support more realistic simulated service environments for more realistic vulnerability verification workflows
  • Upgrade the sandbox integration from function_call to a stable MCP service
  • Auto-Fix: allow agents to directly submit PRs to fix vulnerabilities
  • Incremental PR audit: continuously track PR changes, intelligently analyze vulnerabilities, and integrate with CI/CD pipelines
  • Optimize RAG: support custom knowledge bases

Contributing & Community

Contributing Guide

We warmly welcome contributions of all kinds, whether that means filing issues, opening PRs, or improving documentation. Please refer to CONTRIBUTING.md for details.

Contact the Author

You are welcome to reach out for technical discussions, feature suggestions, or collaboration opportunities. For platform customization, code auditing services, technical consulting, or business collaboration, please contact by email.

Contact
Emaillintsinghua@qq.com
GitHub@lintsinghua

License

This project is open-source under the AGPL-3.0 License.

Project Popularity

Star History Chart
Made with ❤️ by lintsinghua

Acknowledgements

Thanks to the following open-source projects for their support:

FastAPI / LangChain / LangGraph / ChromaDB / LiteLLM / Tree-sitter / Kunlun-M / Strix / React / Vite / Radix UI / TailwindCSS / shadcn/ui


Important Security Notice

  1. Any unauthorized vulnerability testing, penetration testing, or security assessment is strictly prohibited
  2. This project is intended only for cybersecurity research, teaching, and learning
  3. It is strictly prohibited to use this project for illegal purposes or for unauthorized security testing

Vulnerability Reporting Responsibility

  1. If you discover any security vulnerability, please report it through legitimate channels in a timely manner
  2. It is strictly prohibited to use discovered vulnerabilities for illegal activities
  3. Comply with cybersecurity laws and regulations and help maintain a secure cyberspace

Usage Restrictions

  • Only use this project in authorized environments for education and research
  • Do not use it for security testing against unauthorized systems
  • Users are solely responsible for their own actions

Disclaimer

The author is not responsible for any direct or indirect losses caused by the use of this project. Users bear full legal responsibility for their own actions.


Detailed Security Policy

For detailed information about installation policies, disclaimers, code privacy, API usage security, and vulnerability reporting, please refer to DISCLAIMER.md and SECURITY.md.

Quick Reference

  • Code privacy warning: your code will be sent to the servers of the selected LLM provider
  • Sensitive code handling: use local models when processing sensitive code
  • Compliance requirements: follow data protection and privacy laws
  • Vulnerability reporting: report security issues through legitimate channels