Aave tightened listing requirements after the rsETH incident involving $293 million - ForkLog: cryptocurrencies, AI, singularity, the future

# Aave tightened listing standards after the rsETH incident involving $293 million

The Aave protocol revised its asset listing standards following the April rsETH incident, which threatened the project with the risk of billions of dollars in bad debt.

https://t.co/ixfuSrVKA8

— Aave (@aave) May 31, 2026

The incident was caused by a verification failure in the LayerZero bridge used by the Kelp project, not a vulnerability in the smart contracts of the lending platform itself. The attacker exploited a configuration error in one of the verifiers to forge a cross-chain message and issued 116,500 uncollateralized rsETH tokens ($293 million).

The assets were deposited into Aave as collateral. Since rsETH was in eMode with a high LTV (93%), the attacker borrowed liquid assets that the protocol would not be able to recover after the rsETH depreciated.

The new framework for versions V3, V4, and Horizon expands risk assessment criteria. Now, in addition to volatility and liquidity, Aave will consider:

• the reliability of bridge infrastructure and the number of token wrapping levels;
• dependence on external oracles and custodians;
• technical architecture (compliance with ERC-20, admin rights, and upgradeability);
• operational security of the asset issuer.

The team also proposed implementing automated protective mechanisms. These will allow instant zeroing of the asset’s LTV when critical risk thresholds are reached, without waiting for management decisions.

Risk managers have already made about 295 adjustments to V3 market parameters, including reducing supply and borrow limits to minimize the impact of similar incidents.

OpenZeppelin auditors confirmed that the incident resulted from misconfigurations in infrastructure and risk management, not bugs in Aave or Kelp code.

Recall that on May 25, Kelp restored rsETH collateral, and the team sent a final tranche of 20,373 rsETH to the LayerZero smart contract.