Venus protocol (vaults)

QuantstampRepository at commit f1426f0

Audit

Part of Quantstamp’s series

Quantstamp reviewed Venus Protocol (Venus protocol (vaults)) on 19 May 2023: 16 findings, 0 critical; 10 marked fixed, 4 acknowledged, 2 open; 4 more marked mitigated.

No open critical findings
Open the reportOpen Venus Protocol’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings25

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixedMitigated
Critical0000
High0030
Medium0040
Low2434
LowInaccurate Pending Rewards for VAI Vault UsersOpen

The VAI vault's `pendingXVS()` function may not return the correct amount of XVS rewards the user is eligible for. This function uses `accXVSPerShare` to calculate the rewards, but `accXVSPerShare` is only updated in `updateVault()`. Therefore, the return of `pendingXVS()` is inaccurate between a `updatePendingRewards()` call and the first call that triggers `updateVault()`. Third-party protocols or front-ends calling `pendingXVS()` during this period will get a lower value than the actual.

LowXVS Vault's Domain Separator Does Not Include a Contract VersionOpen

The domain separator calculated for the XVS vault does not include a `version` field. According to [EIP-712](https://eips.ethereum.org/EIPS/eip-712), > `string version` the current major version of the signing domain. Signatures from different versions are not compatible. Without the `version` field, a signature signed for the current version of the contract can be reused in future versions as long as the current nonce does not change, which can be an issue since the contract may be upgraded again in the future.

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.

Repository and files the report names (7)

  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSVaultStorage.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a
  • https://github.com/VenusProtocol/venus-protocol/contracts/Vault/VAIVaultStorage.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a
  • https://github.com/VenusProtocol/venus-protocol/contracts/VRTVault/VRTVaultStorage.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a
  • https://github.com/VenusProtocol/venus-protocol/contracts/Vault/VAIVault.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSVault.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSStore.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a
  • https://github.com/VenusProtocol/venus-protocol/contracts/VRTVault/VRTVault.sol at commit f1426f07b44f9b557059a0e364ce5d90e18f997a

Part of Venus Protocol’s security record

Venus Protocol
Audits67 audits by 7 firmsLast audit Sep 2025, by Quantstamp.
Critical findingsNo open critical findingsAcross the 67 reports, 4 critical findings were reported. Each is marked fixed by the firm that reported it.
IncidentIncident 12 May 2022Source: De.Fi incident database.
Open Venus Protocol’s security record

Security firm

Quantstamp

240 projects reviewed · 338 reports · latest Nov 2026

See Quantstamp’s audits

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