# EigenPods Bug Fix Completed - August 29 2025

**URL:** <https://forum.eigenlayer.xyz/t/eigenpods-bug-fix-completed-august-29-2025/14713>\
**Category:** Protocol Updates\
**Created:** [August 29, 2025, 5:53pm UTC](https://forum.eigenlayer.xyz/t/eigenpods-bug-fix-completed-august-29-2025/14713 "2025-08-29T17:53:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![graceh](https://avatars.discourse-cdn.com/v4/letter/g/a183cd/32.png) [@graceh](https://forum.eigenlayer.xyz/u/graceh)\
**Post date:** [August 29, 2025, 5:53pm UTC](https://forum.eigenlayer.xyz/t/eigenpods-bug-fix-completed-august-29-2025/14713/1 "2025-08-29T17:53:45Z")

</div>

**EigenPods Bug Fix Completed - August 29 2025**

The community multisig has completed an urgent bug fix on EigenPods that could have impacted the rewards distribution feature and inflated slashable security values.

**What Happened**  
An Immunifi bug report uncovered the following: A malicious EigenPod user can mint more beacon chain shares than they actually have by abusing withdrawal mechanics introduced with Pectra. This leads to situations where a Pod owner will receive inflated rewards and AVSs could experience miscalculated slashable stake values. Our on chain analysis reveals that **no user has called this function to begin the exploit path**. Given the Ethereum exit queue length of 15 days, we are taking immediate action to resolve this bug before it can be abused.

**Risk & Impact**

- No customer funds at risk.

- No evidence of the bug being exploited backed by onchain data.

- Service remained uninterrupted.

**Why We Upgraded**

Even though no customers were affected, we prioritized this patch to eliminate the potential for abuse and uphold best security practices.

**Details**

- **Timing:** Completed August 29, 2025

- **Where:** Mainnet and Testnets

- **Impact to Customers:** None

- **Action Required:** None

- **Service Impact:** No downtime, EigenPods continues to operate normally

**More Information**

For a detailed explanation, please see the [Release Notes here](https://github.com/Layr-Labs/eigenlayer-contracts/releases/tag/v1.6.1).

---

<div class="post-metadata">

**Author:** ![Rochelle](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@Rochelle](https://forum.eigenlayer.xyz/u/Rochelle)\
**Post date:** [October 26, 2025, 8:38pm UTC](https://forum.eigenlayer.xyz/t/eigenpods-bug-fix-completed-august-29-2025/14713/2 "2025-10-26T20:38:51Z")

</div>

The detailed communication around timing, scope, and customer impact is exactly what builds confidence in the protocol’s security posture. Glad to hear there was no interruption of service and no user funds at risk.`