Key Highlights
- Cosmos Labs said many chains affected by the Cosmos EVM security incident have now applied patches.
- Networks running Cosmos EVM versions earlier than v0.6.2 or v0.7.2 have been advised to immediately halt operations and upgrade.
- The organization continues to provide mitigation guidance to affected networks and is coordinating remediation with chain teams.
Cosmos Labs, a Layer 1 blockchain stack builder, said on Wednesday that many chains affected by an ongoing security incident involving the Cosmos EVM module have applied patches.
In an update posted to its verified X account, Cosmos Labs recommended that any chain running a Cosmos EVM version earlier than v0.6.2 or v0.7.2 immediately halt its blockchain and upgrade to include the available patches. Teams using Cosmos EVM that have not yet supplied security contact details were asked to write an email to Cosmos.
Background on the incident
The advisory follows a statement issued on August 24, 2026. At that time, Cosmos Labs reported an ongoing security incident involving users of the module. The firm said its security and engineering teams were responding and advised Cosmos EVM chains in contact with it to request that their validators halt operations.
The August 24 statement did not identify the specific vulnerability, name the affected chains, or provide figures on any losses. Cosmos Labs said a full incident report would be released once the situation was resolved.
A number of Cosmos SDK networks that support Ethereum-compatible smart contracts through the shared Cosmos EVM stack went offline in succession around the time of the initial advisory. The broader warning expanded the response beyond individual chain decisions to a general notice directed at Cosmos EVM operators in communication with the laboratory.
Current status and upgrade guidance
The Wednesday update stated that many of the affected chains have now patched. Cosmos Labs said it is still supplying mitigation information to networks that require it.
The explicit recommendation remains that chains on versions below v0.6.2 or v0.7.2 should halt and upgrade without delay.
The latest statement did not provide additional details about the vulnerability, the number of chains involved, or any financial impact. As with the earlier communication, Cosmos Labs said a comprehensive post-mortem would follow at a later date.
Scope of the incident
The incident centers on the Cosmos EVM module, which enables Ethereum-style smart contract functionality on Cosmos SDK chains. Because the module is shared infrastructure, a vulnerability in it can affect multiple independent networks that have integrated the same codebase.
Until the promised incident report is published or independent on-chain evidence becomes available, the full scope of the event, including which specific chains were compromised, whether funds were lost, and the precise technical vector, remains unconfirmed. Operators and users have been advised to treat earlier reports with caution pending official clarification.
Cosmos Labs has maintained a single point of contact for security matters throughout the episode. Chains that have not yet registered their security teams were again encouraged to do so. The organization has not set a public timeline for the final report.
The statements on August 24 and August 26 represent the primary public information released by Cosmos Labs on the matter to date. Further updates are expected once remediation across the affected networks is complete and the organization finishes its review.
Other security incidents in August 2026
Several other blockchain projects have reported security incidents during August.
Chainflip detected and contained an attempted exploit targeting its cross-chain messaging and refund logic on Ethereum within about 24 hours. No user funds were lost, and the network was restored after an upgrade.
BounceBit reported an authorization flaw that allowed an attacker to move roughly 286.5 million BB tokens (approximately $3 million) at the time. The project subsequently shut down its Layer 1 and reissued BB as a BEP-20 token on BNB Chain.
Ledger quietly patched a race-condition vulnerability in its Ethereum app’s clear-signing flows on 12 August; no confirmed fund losses were reported. Harmony experienced large-scale illicit minting of ONE tokens through cross-shard verification flaws and announced a full network rollback to the pre-exploit state.
Also Read: Solana’s New Tokenomics Could Squeeze Staking Returns: 21Shares
