Pendle Immunefi Bug Bounty Disclosures

Pendle's Immunefi bug bounty program serves as a primary filter for critical vulnerabilities before they can be exploited in production. The disclosures analyzed on this page represent the most severe findings—those that could have led to direct loss of user funds, manipulation of PT/YT pricing, or a breakdown of core yield tokenization logic. Each disclosure is a case study in the protocol's security boundaries, revealing how external researchers probe the PendleMarket, PendleYieldContractFactory, and custom AMM contracts for flaws in rounding, access control, and composability assumptions.

The vulnerability patterns observed in these disclosures often cluster around the complex interaction between Pendle's permissionless market creation and its TWAP oracle design. A recurring theme is the economic manipulation of implied yield, where a bug in swap curve logic or a rounding error in the _getRateImpl function can be exploited via flash loans to extract value from liquidity providers. Other high-severity findings target the vePENDLE vote-escrow system, where a flaw in reward distribution or gauge weight calculation could allow an attacker to redirect incentives. These patterns inform the specific attack vectors that integrators must model when building lending markets, yield aggregators, or structured products on top of PT/YT tokens.

For security teams and whitehats, this page provides a structured map of Pendle's historical vulnerability classes, the affected contract versions, and the implemented fixes. Understanding these patterns is essential for both bug hunting and defense. For protocol architects and risk managers, the disclosures highlight the systemic risks that require continuous monitoring—particularly the dependency on correct TWAP calculation and the integrity of external oracle feeds. Teams integrating Pendle should use these disclosures to inform their own internal threat models and to verify that their integration logic correctly handles the edge cases that have historically led to critical findings. Chainscore Labs can assist with a targeted review of your integration against these known vulnerability classes.

Analysis of Pendle's Immunefi bug bounty disclosures reveals a distinct set of recurring vulnerability patterns centered on the protocol's unique financial primitives. The most critical class of bugs involves rounding errors and precision loss in the core PendleMarket and AMM math libraries. Because Pendle's PT/YT tokens represent a zero-sum relationship where precision determines the exact split of yield, even a single-wei miscalculation in _computeSYOutput or _computePYOutput can be exploited across multiple transactions to systematically drain value from one side of the pool. These vulnerabilities are not typical smart contract logic errors but are deeply embedded in the fixed-point arithmetic assumptions of the protocol's yield tokenization engine.

A second dominant pattern involves oracle manipulation vectors specific to Pendle's TWAP implementation and its dependency on external price feeds for the underlying yield-bearing asset. Researchers have demonstrated attacks where flash-loan-induced manipulation of the underlying asset's exchange rate cascades into a mispricing of the implied yield, allowing an attacker to mint PT/YT at a fraudulent discount. The root cause is often a failure to apply sufficient manipulation resistance or to properly bound the acceptable deviation between the internal TWAP and the external oracle price before allowing state-changing operations. This class of vulnerability highlights the systemic risk created by Pendle's composability with external DeFi primitives.

A third critical pattern concerns access control and authorization flaws in Pendle's permissionless market creation architecture. The PendleYieldContractFactory allows any address to deploy a new market for any yield-bearing token, which introduces an attack surface where a maliciously designed token contract can re-enter the Pendle core during market initialization or exploit callback assumptions in the approve and transfer flows. Several high-severity disclosures have identified scenarios where a custom token's transfer hook could manipulate the state of the newly deployed PendleMarket before the initialization transaction completes. Security teams and integrators should treat every new market deployment as a potential vector and verify that their own systems do not blindly interact with unverified PT/YT contracts. Chainscore Labs can assist with a targeted review of your market interaction logic and dependency on the factory's permissionless deployment model.