Wrong vesting position upper tick passed to `collectFees` will block vesting position funds and claiming fees

Wrong univ3 swap path check leads to OOG and DoS for Leverage positions where the swap path has more than one swap

Limited veRaac Token Supply Triggers DoS, Hampering Proper Governance Participation.

`FeeCollector::updateFeeType` wrong fee share validation leads to impossible update for some fee types

Platform fees withdrawal will sweep oracle agents earned fees

TokenManager - Unlimited withdraw

`listOffer` Unsafely References Fungible Identifiers

Forger Entities can forge more times than intended

Each generation should have 1 "Golden God" NFT, but there could be 0

Incompatibility with Multisig Wallets in `TempleGold::send` Function

Selling sUSDe is vulnerable to sandwich attack when staked token is DAI

StakingToken.sol doesn't properly handle FOT, rebasing tokens or those with variable which will lead to accounting issues downstream.

Malicious User can call `lockOnBehalf` repeatedly extend a users `unlockTime`, removing their ability to withdraw previously locked tokens

`executeWithdraw` may be blocked if any of the users are blacklisted from the `baseToken`

PrismaConnector can mint a position below the desired health factor

It is possible to open insolvent position is Silo connector, due to missing check in borrow function

PendleConnector.sol::supply doesn't pass a valid slippance protection min

The `TVLHelper.sol#getTVL` function is DOSed by the `under collateralized connector`, and as a result, many parts of the protocol may be DOS.

The modifier `onlyExistingRoute` works incorrectly

Chainlink connector doesn’t check for the Min / Max prices returned

`Keepers` does not implement EIP712 correctly on multiple occasions

Lack of Slippage Controls in retrieveTokensForWithdraw Function

If a curve pool which CurveConnector uses is killed the vault manager can't close the position leading to loss of funds

Balancer flashloan contract can be DOSed completely by sending 1 wei to it

Using the same heartbeat for multiple price feeds

A malicious user can front-run Morpho repay with a small repay amount making the transaction revert for underflow, DoSing the repay

Inability to perform partial liquidations allows huge positions to accrue bad debt in the system

Attacker can frontrun to prevent vaults from being removed from the dNFT owner's position

The `BURNER` cannot burn tokens from accounts not KYC verified due to the check in `_beforeTokenTransfer`.

External swap fee would also be applied to native swaps

Any fee claim lesser than the total `yieldFeeBalance` as unit of shares is lost and locked in the `PrizeVault` contract

User wrapped tokens get stuck in master router because of incorrect calculation

Malicious user can stake an amount which causes zero curStakeAtRisk on a loss but equal rewardPoints to a fair user on a win

Since you can reroll with a different fighterType than the NFT you own, you can reroll bypassing maxRerollsAllowed and reroll attributes based on a different fighterType

Players have complete freedom to customize the fighter NFT when calling `redeemMintPass` and can redeem fighters of types Dendroid and with rare attributes

FighterFarm:: reroll won't work for nft id greator than 255 due to input limited to uint8

NFTs can be transferred even if StakeAtRisk remains, so the user's win cannot be recorded on the chain due to underflow, and can recover past losses that can't be recovered(steal protocol's token)

Can mint NFT with the desired attributes by reverting transaction

Fighter created by mintFromMergingPool can have arbitrary weight and element