Skip to content
Fencer Vulns
critical 9.3

CVE-2026-61604 json

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

published 2026-09-24 45 d ago modified 2026-10-01 38 d ago also GHSA-w3rp-4cm2-4wgc , GO-2026-6595 , EUVD-2026-86330

cvss
9.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/ixofoundation/ixo-blockchain/v8 8.0.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
45 d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA 4.0 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
go github.com/ixofoundation/ixo-blockchain/v8
<8.0.0
8.0.0
go github.com/ixofoundation/ixo-blockchain/v7
<=7.0.0
all versions
 no fix listed
go github.com/ixofoundation/ixo-blockchain/v6
<=6.0.1
all versions
 no fix listed
go github.com/ixofoundation/ixo-blockchain/v5
<=5.0.0
all versions
 no fix listed
go github.com/ixofoundation/ixo-blockchain/v4
<=4.0.0
all versions
 no fix listed
go github.com/ixofoundation/ixo-blockchain/v3
<=3.0.0
all versions
 no fix listed
go github.com/ixofoundation/ixo-blockchain
<=1.6.0
all versions
 no fix listed

Affected products

  • ixofoundation ixo-blockchain

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.