Vulnerabilities / CVE-2026-61604

critical

CVE-2026-61604

ixo Blockchain x/bonds DID-resolved payer drain + x/entity ICA authorization bypass

Published Modified CWE 285, 862
In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

GHSA9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Trivy's own label is CRITICAL. Rated critical by GHSA.

Description

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.

Affected packages and fixed versions

SourcePackageFixed in
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain, github.com/ixofoundation/ixo-blockchain/v3, github.com/ixofoundation/ixo-blockchain/v4 and 4 more8.0.0
Show all 7 entries from 1 source
SourcePackageFixed in
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchainno fix listed
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v3no fix listed
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v4no fix listed
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v5no fix listed
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v6no fix listed
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v7no fix listed
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v88.0.0

References

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.