cve.bz

CVE-2026-61604 ixofoundation ixo-blockchain: Improper Authorization

9.3 criticalEPSS 0.3%Fix available

Critical (9.3) in ixofoundation ixo-blockchain. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/ixofoundation/ixo-blockchain/v8 8.0.0.

On this page
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.

Severity

CVSS 4.0

9.3 critical
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
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-09-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-285 Improper Authorization
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/ixofoundation/ixo-blockchain/v8 (Go): fixed in 8.0.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-61604 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61604?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61604?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61604 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ixofoundation ixo-blockchain< 8.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain/v8<8.0.08.0.0
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain/v7<=7.0.0no fix published
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain/v6<=6.0.1no fix published
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain/v5<=5.0.0no fix published
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain/v4<=4.0.0no fix published
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain/v3<=3.0.0no fix published
GHSA-w3rp-4cm2-4wgcGogithub.com/ixofoundation/ixo-blockchain<=1.6.0no fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchainall versionsno fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchain/v3all versionsno fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchain/v4all versionsno fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchain/v5all versionsno fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchain/v6all versionsno fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchain/v7all versionsno fix published
GO-2026-6595Gogithub.com/ixofoundation/ixo-blockchain/v8<8.0.08.0.0

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-285 (16).

References

Check your stackJSON