CVE-2026-61604
CriticalCVSS 9.3Summary
Prior to version 8.0.0, the x/bonds module of the ixo Blockchain moved funds from an address resolved from a DID verification method without verifying that the resolved address belonged to the transaction signer. An attacker could register victims' addresses as verification methods on their own DID and move victims' balances into an attacker-controlled bond, later withdrawing and bridging the proceeds off-chain. This was exploited on ixo mainnet (ixo-5) on 2026-06-20 and fixed in v8.0.0.
Risk Assessment
Any account holding a balance in a token a bond could use was at risk, with no victim keys, signatures, or system compromise required. The attack has already been executed on mainnet, resulting in real loss of funds.
Recommendation
All node operators and validators must immediately upgrade to v8.0.0 via the on-chain software upgrade. There is no application-level workaround — remediation requires running the patched binary, and the bonds module remains disabled until a future release.
Related vulnerabilities
- CVE-2026-95699Critical
Prior to 9/18/2026, the iSteamX mobile application's AWS policy could grant authenticated users access to wildcard MQTT topics, which can expose other users' device data and allow the attacker to start and stop other connected users' devices. This risked exposing user profile information and potential scalding due to unintended device activation.
- CVE-2026-93291Critical
Omni C20 lacks proper certificate validation which could allow an attacker to perform a man-in-the-middle attack which could allow them to execute arbitrary code.
- CVE-2026-86860Critical
ServiceNow has remediated a missing authorization vulnerability that was identified in the ServiceNow AI Platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to extract instance data beyond what was intended, resulting in privilege escalation.
- CVE-2026-13249Critical
An unauthenticated Remote Code Execution via Arbitrary File Upload vulnerability in the web management interface in Honeywell PD45 Industrial Printer version F10.19.010040, allows upload of attacker controlled files without requiring authentication.
- CVE-2026-13016Critical
ServiceNow has remediated a SQL injection vulnerability that was identified in the ServiceNow AI Platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute arbitrary SQL statements against the instance's underlying database and gain access to, or modify, instance data beyond what was intended.
- CVE-2026-61742Critical
DBHub, a database MCP server, in versions prior to 0.22.5 exposes an unauthenticated HTTP MCP endpoint when started in HTTP transport mode. Its protection based on comparing Origin and Host headers does not prevent DNS rebinding, allowing a malicious website to invoke MCP tools from the victim's browser. Depending on configuration, this can lead to reading, enumerating, and potentially writing database contents.
- CVE-2026-61741Critical
The http4s-scala-xml library in versions prior to 0.24.1 and 1.0.0-M39 uses a SAXParserFactory without security configuration to decode XML message bodies. With default JDK settings, the parser resolves DOCTYPE declarations, external entities, and external DTDs. Applications parsing untrusted XML are vulnerable to XXE, SSRF, and resource exhaustion attacks.
- CVE-2026-61732Critical
Decepticon, an autonomous hacking agent for red teams, in versions prior to 1.1.17 wraps web crawl results into LLM messages without neutralizing ChatML special-token literals. Under the BYOK model, most model providers do not filter these literals, so an attacker can plant them on a target page to forge an operator turn and bypass agent guardrails. This results in arbitrary command execution inside the Kali Linux sandbox.
- CVE-2026-79766Critical
In Termix from 2.4.1 until 2.5.1, an authenticated Termix administrator can store attacker-controlled domain and email values through PATCH /users/acme-ssl-settings and trigger their interpolation into a certbot shell command through POST /users/acme-ssl-request. In acme-ssl-routes.ts, child_process.execSync invokes /bin/sh -c with those values only wrapped in double quotes, so shell metacharacters can execute arbitrary operating-system commands as the Termix backend process. Both HTTP webroot and DNS Cloudflare challenge modes are affected, and compromise exposes Termix databases, process secrets, stored credentials, and network reachability. This issue is fixed in version 2.5.1.
- CVE-2026-93425Critical
In Dokploy prior to 0.29.13, the patch.readRepoDirectories tRPC procedure passes the user-controlled repoPath value from patch.ts into a shell command in patch-repo.ts without safe argument quoting. An authenticated organization member with service:read permission can inject shell metacharacters into repoPath and execute arbitrary commands through child_process.exec as root in the Dokploy container. Because the standard deployment mounts /var/run/docker.sock, container-root command execution can be used to control Docker and compromise the host and its managed applications. This issue is fixed in version 0.29.13.
Original NVD description (English source)
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.

