Attestkeep
Langue : Français
S'inscrire

Vulnérabilités / CVE-2026-61604

critique

CVE-2026-61604

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

Publiée Modifiée CWE 285, 862
Dans la Trivy database depuis au moins le 24 oct. 2026, 07:11 UTCLa date d'entrée avant ce build n'est pas enregistrée.

Sévérité par 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

Le label propre à Trivy est CRITICAL. Critique selon 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.

Paquets affectés et versions corrigées

SourcePaquetCorrigé en
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain, github.com/ixofoundation/ixo-blockchain/v3, github.com/ixofoundation/ixo-blockchain/v4 et 4 autres8.0.0
Afficher les 7 entrées d'une source
SourcePaquetCorrigé en
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchainpas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v3pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v4pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v5pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v6pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v7pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/ixofoundation/ixo-blockchain/v88.0.0

Références

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.