CVE Catalog

CVE-2026-61604

CriticalCVSS 9.3
Published: Updated: Translated: NVD NIST

Summary

Prior to version 8.0.0, the x/bonds module of the ixo Blockchain moved funds from an address resolved from a DID verification method without verifying that the resolved address belonged to the transaction signer. An attacker could register victims' addresses as verification methods on their own DID and move victims' balances into an attacker-controlled bond, later withdrawing and bridging the proceeds off-chain. This was exploited on ixo mainnet (ixo-5) on 2026-06-20 and fixed in v8.0.0.

Risk Assessment

Any account holding a balance in a token a bond could use was at risk, with no victim keys, signatures, or system compromise required. The attack has already been executed on mainnet, resulting in real loss of funds.

Recommendation

All node operators and validators must immediately upgrade to v8.0.0 via the on-chain software upgrade. There is no application-level workaround — remediation requires running the patched binary, and the bonds module remains disabled until a future release.

Related vulnerabilities

Original NVD description (English source)

The ixo Blockchain is a Layer 1 blockchain that runs on both Testnet and Mainnet. Prior to version 8.0.0, the x/bonds module moved funds from an address that was resolved from a DID verification method, without verifying that the resolved address belonged to the transaction signer. Affected handlers included MsgMakeOutcomePayment, MsgBuy, MsgSell, MsgSwap, and MsgWithdrawShare, as well as the batch order processor. Because any account may list an arbitrary blockchainAccountID as a verification method on a DID it controls (without the consent of that address's owner), an attacker could register victims' addresses as verification methods on their own DID and then move the victims' balances into a bond the attacker controlled — later withdrawing and bridging the proceeds off-chain. This was exploited on ixo mainnet (ixo-5) on 2026-06-20. The attack required no victim keys, signatures, or system compromise — any account holding a balance in a token a bond could use was at risk. This was fixed in v8.0.0, delivered via the on-chain v8 software-upgrade. The x/bonds module is disabled: every bonds message is rejected on all routes (top-level, authz, CosmWasm, and ICA), and the bonds batch EndBlocker is a no-op so no further reserve movements can occur. All node operators and validators must upgrade to v8.0.0. The flaw is in chain state-machine logic and can only be remediated by running the patched binary. There is no application-level workaround. The vulnerability is in consensus logic; remediation requires the network to run the patched (v8.0.0) binary. The bonds module remains disabled in v8.0.0 and will only be re-enabled in a future release once the signer-authorization model has been corrected.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS