> For the complete documentation index, see [llms.txt](https://docs.infraredtrading.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraredtrading.com/learn/protocols/morpho/security.md).

# Security

Morpho's trust model follows directly from its design (see [Mechanics](/learn/protocols/morpho/mechanics.md)): the **core is immutable and minimal**, so most realized risk lives at the **curation layer** — which oracle a market uses, and which markets a vault allocates into — rather than in the Morpho Blue contract itself.

## Audits

Morpho's core and periphery have been reviewed by multiple firms, with the reports published in the respective GitHub repositories and catalogued on the [official audits page](https://docs.morpho.org/get-started/resources/audits/):

* **Morpho Blue (core)** — reviews by OpenZeppelin (Oct 2023), a Cantina/Spearbit-managed review (Nov 2023), and a Cantina competition (Jan 2024), plus a separate Cantina review of the IRM periphery (Feb 2024).
* **MetaMorpho / Vaults V1** — Cantina managed review (Nov 2023), OpenZeppelin periphery (Nov 2023), a Cantina competition (Jan 2024), and an OpenZeppelin review of the V1.1 diff (Nov 2024).
* **Vault V2** — ten reports across 2025 from Spearbit, a Cantina competition, Zellic, Blackthorn, ChainSecurity, and Certora (including the Market-V1 adapter). ChainSecurity also published a dedicated audit page for this engagement.

Morpho's risk documentation summarizes the cumulative record as dozens of audits across many firms. [audits](https://docs.morpho.org/get-started/resources/audits/)

## Formal verification

Beyond audits, Morpho applies **formal verification** with Certora (CVL) and Halmos (symbolic execution) across the core (Dec 2023), Vaults V1 (Mar 2024), the rewards distributor, pre-liquidation logic, the MORPHO token, the math utilities, and the Vault V2 adapter (Dec 2025). For MetaMorpho, the proofs cover role-hierarchy correctness (senior roles can perform every junior-role action; permissioned operations genuinely require their role), timelock protection of risk-increasing actions, and liveness of emergency functions. [formal-verification](https://docs.morpho.org/learn/resources/formal-verification/)

## Trust boundaries

* **Oracle risk (primary).** A market's oracle sets both the liquidation trigger and the seizure price, is chosen freely without a whitelist, and is immutable. A wrong or manipulable oracle can cause spurious liquidations or under-collateralized borrowing; the only remedy is a new market.
* **Permissionless market creation.** Anyone can create a market with any assets and oracle and any approved LLTV. Risky markets exist by design; a lender using the raw Blue interface bears full responsibility for market and oracle selection.
* **Curator risk (vaults).** A vault curator chooses markets, caps, and allocations, and the owner can replace the curator. Depositors rely on the curator's judgment and on the security of the owner key — single-EOA ownership is explicitly discouraged in favor of a multisig/MPC.
* **Isolation as containment.** Because markets are isolated, bad debt or a bad oracle stays confined to the affected market and vault and cannot cascade protocol-wide — borne out repeatedly in the incidents below.
* **Counterparty/asset risk.** Issuer-level actions on an underlying token (e.g. a stablecoin blacklist) can still impair positions. [risks](https://docs.morpho.org/learn/resources/risks/)

## Incidents

Morpho's incident history illustrates the trust model: the failures came from the curation/oracle layer, and isolation contained them.

* **October 2024 — PAXG/USDC oracle misconfiguration (\~$230K).** A permissionlessly-created market used an oracle with a wrong decimal scale factor (PAXG has 18 decimals, USDC 6), pricing PAXG far above its real value; an attacker turned a few hundred dollars of collateral into \~$230K. This was a market-level configuration error by the market's creator, not a core-contract bug, and the loss was confined to that single market.
* **April 2025 — frontend/SDK incident (no net loss).** An SDK update mis-routed token approvals to a bundler contract rather than its access-controlled adapters, creating a front-running exposure; a whitehat intercepted the transaction and returned the funds, and the team rolled back the change within minutes. No smart contract was affected. [april-2025](https://morpho.org/blog/morpho-app-incident-april-10-2025/)
* **June 2023 — legacy Optimizer vulnerability (bounty, no loss).** An index-caching flaw in the legacy Morpho Optimizer (not Blue) was responsibly disclosed via Immunefi; a $285K bounty was paid and a fix shipped before any exploitation. [june-2023](https://morpho.org/blog/vulnerability-report-june-2023/)
* **November 2025 — curator vault bad debt.** A curator's vault had allocated to a market backed by a synthetic stablecoin that collapsed, producing realized bad debt of a few percent of that vault's value (more on its smaller cross-chain equivalent). Only one of roughly 320 vaults had direct exposure — isolation again contained the contagion.
* **March 2026 — Resolv USR depeg (curator-vault exposure; core unaffected).** A compromised signing key at the Resolv stablecoin issuer minted a large amount of unbacked USR — an issuer-side access-control failure, not a Morpho contract bug — and USR depegged sharply. The depeg impaired curator vaults that held USR-based collateral; Morpho's co-founders publicly confirmed that roughly 15 of about 500 vaults had non-negligible exposure and reiterated there was no vulnerability in Morpho's contracts. Isolation confined the impact — lower-risk "prime" vaults were unaffected. (Specific dollar figures come from third-party estimates.)
* **April 2026 — KelpDAO rsETH bridge exploit (isolation, empirically).** A cross-chain bridge misconfiguration let attackers mint a large amount of unbacked rsETH — the largest DeFi hack of 2026, again outside Morpho. Because Morpho's rsETH markets are isolated, Morpho's exposure was reported at around $1M across two markets, versus a far larger reported exposure (on the order of $177–230M) for a shared-pool lending competitor in the same event — the clearest real-world illustration to date of isolation containing contagion. (Figures come from news reporting.)
* **July 2026 — Summer.fi vault exploit (Morpho used as a flash-loan source, not exploited).** An attacker used a Morpho flash loan as working capital to manipulate the share/asset accounting of a third-party vault (Summer.fi's Lazy Summer product), netting several million dollars. Morpho's flash-loan feature behaved exactly as designed and took no loss — **Morpho was the liquidity source, not the victim**; the flaw was in the other protocol's vault accounting.

## Bug bounty

Morpho runs concurrent bug-bounty programs (on Immunefi and Cantina) with rewards up to **$2.5M** each, covering Morpho and Morpho Vaults. Internal practice adds mutation testing, fuzzing, invariant testing, and internal code-breaking exercises. [immunefi](https://immunefi.com/bug-bounty/morpho/)

## Net read

The core primitive has a strong audit and formal-verification record and an immutable, minimal-surface design. Every realized loss to date has originated **outside the Morpho core** — at the oracle/curation layer or in a market's collateral asset or an external counterparty — and been contained by market isolation, with the 2026 KelpDAO event the clearest empirical contrast to a shared-pool design. The practical takeaway for anyone integrating Morpho is that risk assessment should focus on **oracle, curator, and collateral-asset selection per market and vault**, not on core-contract solvency.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraredtrading.com/learn/protocols/morpho/security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.