Vulnerabilities
Smart Contract Vulnerabilities: OWASP Top 10 and SWC Registry
The OWASP Top 10 and the SWC Registry side by side, and the vulnerability classes that matter most in practice.
Each finding with its protocol, severity, link, and CVE identifier where one was assigned.
3 underconstrained bugs in the DivRem circuit, caught by Picus before external audits
// Picus1 of the 3 critical soundness bugs fixed ahead of the V2 prover upgrade, caught by Picus
// Picus6 underconstrained circuits caught by Picus, 4 of them critical, among 35 issues mitigated during development
// Picus6 issues found by line-by-line manual review before the first production deployment: 1 high, 2 medium, 3 low
// Manual reviewNo finding matches these filters.
Quotes from the teams in the register, taken from their published case studies.
Inventor of Picus, Shankara Pailoor, showed up to the first meeting with two underconstrained bugs already in hand before we had even started to work together, which he had found automatically by running the tool on our ZK circuit code. Needless to say, we chose them, and we’ve been collaborating on ‘full proofs of determinism’ for the ZK circuits ever since.
AuditHub has an amazing tool, Picus, which enables RISC Zero to verify and prove the determinism of our ZK circuits. AuditHub integrated into our CI/CD and performs automated checks while we continue making improvements to our code. Amazing work!
It [AuditHub] gave us a deeper understanding of our own protocol. Developers get closed-minded about their own code after a while. Having auditors go over it, spotting what could get misdiagnosed during development, was critical.
It’s rare to come out of an engagement with real confidence that a class of bugs is absent. Formal verification gave us that.
A finding is listed once it is fixed and the protocol has agreed to be named.
A security tool or a manual review reports the bug, and AuditHub tracks it.
// 001The team fixes it, and the fix is confirmed before anything is published.
// 002We ask the protocol for explicit permission to name it. No permission, no entry.
// 003The row links to the public case study, with a CVE identifier where one was assigned.
// 004Many teams work with AuditHub without announcing it. Their names, their findings and their results are not published anywhere, and they only appear here if they say so. The register shows the teams that chose transparency, so it counts what is public, not everything AuditHub has found.
Vulnerabilities
The OWASP Top 10 and the SWC Registry side by side, and the vulnerability classes that matter most in practice.
DeFi Hacks
What DeFi hacks have in common, read through public post-mortems of real exploits.
AI agents review your code, and security tools bring the evidence.