Incorrect decimal handling in `Auction::buy()` leads to massive overpayment for ZENO tokens

RAACNFT mint function receives funds to address(this) but has no way of withdrawing them

Multiple issues from unnecessary balance increase calculation in DebtToken.mint

Reward manipulation vulnerability in StabilityPool

Incorrect Reward Claim Logic in FeeCollector::claimRewards Causes Denial of Service

Users can borrow more assets than they have deposited as collateral

NFTs Get Permanently Locked in Stability Pool After Liquidation

RToken is Not Interest Bearing Due to Broken Liquidity Index Calculation

Incorrect Debt Scaling Leading to Protocol Solvency Risk

Ownership Parameter Mismatch in LendingPool’s Vault Withdrawal Logic

Untracked Direct Fee Transfers from RAACToken to FeeCollector Break Fee Distribution System

Voting Power Snapshot Missing

Incorrect accounting in `veRAACToken::emergencyWithdraw` and `veRAACToken::withdraw` due to missing `totalLocked` update

Incorrect utilization rate forces protocol to issue maximum rewards indefinitely

Incorrect DebtToken totalSupply Scaling Breaks Interest Rate Calculations

RToken.transferFrom() Does Not Scale User Balances Due to Stale Liquidity Index

LendingPool deposits do not work with CurveVault due to lack of funds

There is no logic checking for RAACNFT price staleness before minting it

`RToken::calculateDustAmount` are incorrectly calculated, leading to not be able to transfer the accrued dust amount

Concurrent Oracle Fulfillments Overwrite House IDs, which leads to Incorrect Pricing

Treasury Contract Deposit Function Can Be Frontrun To Deny Protocol Operations

Emergency revoke in RAACReleaseOrchestrator will freeze revoked RAAC tokens in orchestrator

[L-1] Inaccurate boost calculations in `veRAACToken` due to wrong input parameter

Failure to update `lastClaimTime` mapping when users claim rewards in FeeCollector Causes Time-Based Reward Calculation Issues

`RAACReleaseOrchestrator::emergencyRevoke()` fails to update `categoryUsed`, leading to token lockup and incorrect accounting

RAACToken burns less tokens than expected when feeCollector is unset

getNormalizedDebt will return a wrong Amount when Timedelta is 0.

Valid new periods are incorrectly rejected due to incorrect tracking of `totalDuration`

`mint` function in RToken contract doesn't return the correct expected values, leading to emission of ReserveLibrary `Deposit` event and LendingPool `Deposit` event with incorrect values.

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

Emergency Timelock Bypass: No Enforced 1-Day Delay for Emergency Actions

Unauthorized Vote Casting Vulnerability

Impossible to rescue funds from `RToken` contract

Missing Pause Functionality in veRAACToken Contract Can Be Abused When Emergency Withdrawal Mechanism Is Activated

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

Incorrect Timestamp Tracking in RAACHousePrice contract

Incorrect Mint() Event Emission in RToken#mint()

Treasury's allocated funds not tracked during withdrawals leads to accounting issue where recepient can receive more than allocated funds.

Incorrect Redemption Rate Applied to Leverage Tokens Due to Unconstrained Market Rate Check

Incorrect period used in `transferReserveToAuction` leads to complete failure of action system and loss of bidders' funds.

USDC blacklist will permanently DOS the Auction contract affecting all users

Users will receive incorrect redemption amounts due to decimal normalization error in market rate calculation

Fee Evasion via LP Token Transfer Resets Deposit Value

quantAMMSwapFeeTake used for both getQuantAMMSwapFeeTake and getQuantAMMUpliftFeeTake.

Wrong Fee Take Function Called in UpliftOnlyExample Causing Incorrect Fee Distribution

Inconsistent timestamp storage when the LPNFT is transferred.

Upgrade Initialization Logic Will Never Execute Due to Incorrect Initializer Usage in CommunityVCS

Insecure randomness leads to manipulation of the raffle winner in ERC20Incentive

Incorrect implementation of the LVDepositNotPaused modifier

Incorrect set up and logic of `referralInfoMap` in `SystemConfig::updateReferrerInfo` function

Native token withdrawal fails until manually approved

Malicious user can drain protocol by bypassing `ASK` offer abortion validation in `Turbo` mode

Token withdrawal fails until someone manually approves spending

[Low-01] Missing Access Control in `CapitalPool::approve()` Function Allows any User to call it to set Allowance Amount `TokenContract` to `type(uint256).max`.

3 `OfferStatus` are never used, and code seems to have contradicting intentions