# Liveness Vulnerability Found: A Patched Mumbai Proposal Is Available

**URL:** https://forum.tezosagora.org/t/liveness-vulnerability-found-a-patched-mumbai-proposal-is-available/5188
**Category:** Research and Development
**Created:** [March 7, 2023, 5:31pm UTC](https://forum.tezosagora.org/t/liveness-vulnerability-found-a-patched-mumbai-proposal-is-available/5188 "2023-03-07T17:31:10Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![noodlestomatojuice](https://forum.tezosagora.org/user_avatar/forum.tezosagora.org/noodlestomatojuice/32/1358_2.png) [@noodlestomatojuice](https://forum.tezosagora.org/u/noodlestomatojuice)
#### Post date: [June 16, 2023, 8:18pm UTC](https://forum.tezosagora.org/t/liveness-vulnerability-found-a-patched-mumbai-proposal-is-available/5188/3 "2023-06-16T20:18:30Z")

</div>

@NomadicLabs thank you for identifying this issue. I would love to hear your thoughts on how the community could bring the patch process on-chain, instead of relying on user activated protocol overrides in scenarios like this.

If you don’t think it’s worth it that’s fine too, I’d love to understand why.

I started a thread about this quite a while back,l: [How can we incorporate the patching of issues found during protocol upgrade testing into the on-chain governance process?](https://forum.tezosagora.org/t/how-can-we-incorporate-the-patching-of-issues-found-during-protocol-upgrade-testing-into-the-on-chain-governance-process/3895).

---

_[View the full topic](https://forum.tezosagora.org/t/liveness-vulnerability-found-a-patched-mumbai-proposal-is-available/5188)._