Vesu security record
As of 30 Oct 2026, Vesu has 10 audit reports by 3 security firms on Trustblock; the latest is by Sherlock, dated 21 Feb 2026. Those reports list no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits10
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Vesu audit | Security firm: Sherlock | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| Vesu audit | Security firm: Sherlock | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| Vesu V2 | Security firm: ChainSecurity | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · chainsecurity.com |
| vesu protocol security review | Security firm: Cairo Security Clan | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
| Vesu protocol security review | Security firm: Cairo Security Clan | Date: | Scope: Repository at commit 5f1274f | No open critical findings | Open · IPFS |
| vesu protocol security review | Security firm: Cairo Security Clan | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
| Vesu protocol security review | Security firm: Cairo Security Clan | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
| Vesu protocol security review | Security firm: Cairo Security Clan | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
| vesu protocol security review | Security firm: Cairo Security Clan | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
| Vesu Protocol Security Review | Security firm: Cairo Security Clan | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
Findings36
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 2 |
| Medium | 0 | 0 | 6 |
| Low | 1 | 4 | 22 |
Highpermissionless rebalancing vulnerable to sandwich attacksvesu protocol security review · Cairo Security Clan · 18 Dec 2024Open
The rebalance contract allows anyone to rebalance a position if its loan-to-value (LTV) deviates from the target LTV. The swap is executed based on user-provided parameters, enabling attackers to exploit the dex price through sandwich attacks. For example, attackers can manipulate the DEX price to profit from collateral value through price manipulation, causing loss to the position. Recommendations include restricting the input amount for swaps to match collateral_delta or debt_delta and introducing access control mechanisms. This issue has been mitigated by the client.
Open the reportLowUsers can front-run to withdraw before bad debt is accountedVesu protocol security review · Cairo Security Clan · 29 Jun 2024Open
The report gives no description here.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
Show this on your site
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Content
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="vesu"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something 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