Vesu audit
Audit · firm’s term: security review
Sherlock reviewed Vesu (Vesu audit) on 21 Feb 2026: 11 findings, 0 critical; 7 marked fixed, 4 acknowledged.
No open critical findings
Findings11
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 3 |
| Low | 0 | 4 | 4 |
MediumBridge middlewares are prone to DOS from small donationsFixed
The report gives no description here.
MediumBridge middlewares claiming can be griefedFixed
The report gives no description here.
MediumEkubo adapter fee collection flag prevents collection of pending fees on full withdrawalFixed
The report gives no description here.
LowBridging middleware cannot be reused across configurationsFixed
The report gives no description here.
LowMissing claim_all_coll_gains operation in UncapDecoderAndSanitizerFixed
The report gives no description here.
LowRedundant approval operation in HyperlaneMiddlewareFixed
The report gives no description here.
LowThe Avnu Middleware initializes the owner twiceFixed
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Part of Vesu’s security record
VesuAudits10 audits by 3 firmsLast audit Feb 2026, by Sherlock.
Critical findingsNo open critical findingsAcross 10 reports.
Open Vesu’s security recordSecurity firm
Sherlock5 projects reviewed · 7 reports · latest Jun 2026
See Sherlock’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us