Categories
CVE-2026-61604

Vulnerability in github.com/ixofoundation/ixo-blockchain/v8 (CVE-2026-61604)

Summary

Vulnerability in github.com/ixofoundation/ixo-blockchain/v8 (CVE-2026-61604). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.0.0 or later.

Original description

The description as published by the source.

Impact

Type: Improper authorization leading to unauthorized movement of user funds.

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.

Patches

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.

Workarounds

There is no application-level workaround. The vulnerability is…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61604 has been found in github.com/ixofoundation/ixo-blockchain/v8.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/ixofoundation/ixo-blockchain/v8 to 8.0.0 or later.
If unsure, ask your IT team or search "github.com/ixofoundation/ixo-blockchain/v8 CVE-2026-61604" on the vendor's site.

CVE-2026-61604 (github.com/ixofoundation/ixo-blockchain/v8) — CWE-285
Patched: 8.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-285) exists in github.com/ixofoundation/ixo-blockchain/v8.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/ixofoundation/ixo-blockchain/v8.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 8.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/ixofoundation/ixo-blockchain/v8' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/ixofoundation/ixo-blockchain/v8' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/ixofoundation/ixo-blockchain/v8 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/ixofoundation/ixo-blockchain/v8 to 8.0.0

    ステージング環境で 8.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/ixofoundation/ixo-blockchain/v8
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.0.0"}]}]
go github.com/ixofoundation/ixo-blockchain/v7
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"7.0.0"}]}]
go github.com/ixofoundation/ixo-blockchain/v6
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"6.0.1"}]}]
go github.com/ixofoundation/ixo-blockchain/v5
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"5.0.0"}]}]
go github.com/ixofoundation/ixo-blockchain/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"4.0.0"}]}]
go github.com/ixofoundation/ixo-blockchain/v3
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"3.0.0"}]}]
go github.com/ixofoundation/ixo-blockchain
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.6.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details