ZK Security Audits
ZK Security Audits: Underconstrained Circuits and Witness Leaks
Why underconstrained signals and witness leaks break ZK circuits, and how to check for them.
ZK Vanguard runs in your CI, groups related findings, and supports custom detectors.
For Circom, Halo2, Zirgen and Plonky3.
Results in seconds to minutes, depending on complexity.

Each detector targets one vulnerability class and looks at both sides of your circuit: the code that computes the witness and the constraints that check it.
// 001
Signals without enough constraints, which let an attacker craft proofs with arbitrary values.
// 002
Private witness data exposed through the structure of the circuit.
// 003
Outputs that depend on values that should not influence them.
// 004
Values the witness computes that the constraints never enforce.
// 005
Components that exist but are not connected to the constraint system.
// 006
Divide by zero and control flow that depends on signal values.
Plus checks for out-of-range signals and unused fields, and custom detectors for your own patterns.
ZK Vanguard reads your circuit without running it. Its detectors compare witness generation with the constraints, and catch the places where the two disagree.
// 001

Circom, Halo2, Zirgen or Plonky3 circuits.
// 002

Pick your detectors, ZK Vanguard checks witness generation and constraints.
// 003

Related findings are grouped, and marking a root cause clears linked false alarms in bulk.
Scout flags a circuit it suspects of leaking a private input. ZK Vanguard checks it and returns the evidence: the signals involved and the exact lines in your circuit.
Scout AI - Findings
Line 18
Private input may leak through a public output
ZK Vanguard - Evidence
Private input leakage detected
The signals involved and the exact lines in your circuit.
// PRIVATE INPUT LEAKAGE
Write detectors for the patterns specific to your circuits and your ZK framework. They run on the same engine as the built-in ones and land in the same findings table.

ZK Vanguard runs in your CI and reports in seconds to minutes, depending on complexity. Every change to your circuits gets a fast first pass during development, not after the fact.
ZK Vanguard catches likely underconstrained signals; Picus proves their absence. Run ZK Vanguard first for a fast pass, then Picus for a guarantee that holds for every input.
Catches likely underconstrained signals in a fast first pass.
// 01 ZK Vanguard
Proves the absence of underconstrained signals, for every input.
// 02 Picus
Explore Picus →ZK Vanguard checks your circuits on every change, so your auditors start on cleaner circuits and spend their time on design and logic. The audit still gives you a signed expert review.
Before audit
During audit
After audit



It examines your circuit code without executing it to find vulnerabilities before deployment. ZK Vanguard looks at both witness generation and constraints, and catches where they disagree.
A signal without enough constraints to fix its value. An attacker can then craft a valid proof with an arbitrary value.
Circom, Halo2, Zirgen and Plonky3.
Seconds to minutes, depending on the complexity of your circuits.
ZK Vanguard catches likely underconstrained signals; Picus proves their absence. They work together: ZK Vanguard runs first for speed, Picus follows with formal verification.
Still have questions? Contact us
ZK Security Audits
Why underconstrained signals and witness leaks break ZK circuits, and how to check for them.
Circom
Write a first Circom circuit, then verify that every signal is constrained the way you intend.
Formal Verification
What a formal proof guarantees about a contract or circuit, and which questions it leaves open.
Run ZK Vanguard on your ZK circuits today.