Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain funded signed Bifrost account
-
DeliveryChoose target registered channel_id
-
ExploitSubmit mint extrinsic with forged channel_id
-
ExecutionInflate channel's recorded mint volume
-
PersistCommission settlement over-pays attacker channel
-
ImpactProtocol value redirected
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a signed Bifrost account able to submit mint transactions to the vtoken-minting or slpx pallet, and at least one registered channel_id to attribute volume to (attacker-controlled or otherwise). The core condition, taken directly from the description, is that the mint path accepts an 'arbitrary registered channel_id' without verifying the caller is authorized to mint on behalf of that channel - so any registered channel is a valid target. Realization of gain is gated on the protocol's commission-settlement process actually running and paying out based on recorded mint volume; the impact is limited to commission/attribution accounting (financial misdirection) and does not by itself grant confidentiality access or halt the chain. The limiting factors are the need for a funded signed account and transaction fees, and dependence on the commission mechanism being active. |
| Impact | The input CVSS of 9.1 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:N) overstates the profile in two ways. First, exploitation requires a signed transaction from a funded on-chain account, which is an authenticated origin - PR:L is more honest than PR:N. Second, the impact is manipulation of commission accounting (integrity/financial misdirection), not disclosure of confidential data, so C:H is not well supported; this reads as an integrity-and-financial issue (I:H, C:N). Corroborating signals point to a real-but-not-urgent-at-scale picture: EPSS is 0.14% (3rd percentile), there is no CISA KEV listing, and no working exploit is published - only a docs link and a GitHub gist. That said, the barrier to abuse is genuinely low (a normal signed extrinsic against default runtime logic), the economic incentive is direct (siphoning protocol commission), and any operator running an affected Bifrost runtime should treat commission-misattribution as a high-priority governance/runtime-upgrade item because the loss is monetary and continuous rather than a one-off. Overall: high real-world severity for anyone running the affected pallets, tempered by the fact that it targets a single niche parachain rather than a broadly deployed product. |
| Exploit ScenarioDerived | An attacker registers or identifies a channel it controls (or targets an existing one), then submits ordinary signed mint extrinsics through vtoken-minting or slpx while passing that channel_id as the attribution key. Over many mints the channel's recorded volume is inflated, and at the next commission settlement the protocol pays that channel a disproportionate share of commission, redirecting protocol value to the attacker. A public gist referencing the issue exists, but no confirmed weaponized exploit is identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 10, 2026
Improper authorization in Bifrost's vtoken-minting and slpx Substrate pallets lets any signed on-chain account attribute its mint volume to an arbitrary registered channel_id it does not control. Because the mint path never verifies that the caller is authorized to mint on behalf of the supplied channel, an attacker can inflate a target (or attacker-owned) channel's recorded mint volume and skew protocol commission settlement so payouts are disproportionately routed to that channel. There is no public exploit identified at time of analysis and EPSS is very low (0.14%), but the flaw directly enables financial value redirection within a live DeFi parachain.
RemediationAI
No vendor-released patched version is identified in the available data - the EUVD entry gives only an affected range ('≤2022.02') and no fixed spec/runtime version, so operators and integrators should track the Bifrost security channel and NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-86840) for the corrective runtime upgrade and apply it via on-chain governance/runtime-upgrade as soon as it is published. As a compensating control until a fixed runtime is enacted, the mint extrinsics should enforce that the supplied channel_id is bound to the signing origin (reject any mint where the caller is not the registered controller of the channel); where governance can act, temporarily disabling or freezing channel-commission settlement prevents attackers from realizing inflated payouts, at the cost of suspending legitimate referral commission accrual. Off-chain, monitor per-channel mint volume for anomalous spikes and reconcile commission settlements before payout so forged attribution can be clawed back or withheld.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Bifrost is a Polkadot/Kusama liquid-staking and cross-chain DeFi parachain built on Substrate; the affected code is in two runtime pallets, vtoken-minting (the core vToken issuance logic) and slpx (the cross-chain/EVM-facing mint entry point). The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): the channel_id used for commission attribution is treated as a trusted, caller-supplied value. Channels are a referral/partner accounting construct - mint activity attributed to a channel earns that channel a share of protocol commission at settlement. Because the extrinsic accepts any registered channel_id without binding it to the signing origin's authorization, the user-controlled key (channel_id) is not validated against the caller's permissions, letting attribution be forged. CPE lists cpe:2.3:a:bitfrost.io:bifrost (the 'bitfrost.io' vendor string appears to be a typo of bifrost.io).
Know when Bifrost gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Requires a signed on-chain account so PR:L not PR:N; impact is forged commission attribution (integrity/financial), so I:H with C:N and A:N.
Primary rating from Vendor (certcc).
CVSS VectorVendor: certcc
Lifecycle Timeline
3DescriptionCVE.org
The vtoken-minting and slpx pallets in Bifrost contain an improper authorization vulnerability in channel commission attribution. A signed account can supply an arbitrary registered channel_id when minting tokens without verifying that the caller is authorized to mint on behalf of that channel. This allows an attacker to inflate a channel's recorded mint volume and cause protocol commission payments to be disproportionately distributed to that channel during commission settlement.
Executive ViewAI
Bifrost's vtoken-minting and slpx Substrate pallets contain an authorization flaw allowing signed protocol accounts to falsely attribute transaction volumes to uncontrolled channels, directly redirecting commissions and compromising the integrity of fee distribution in a live DeFi system where payouts depend on accurate volume attribution.
Require multi-signature approval for all channel registrations and high-value mint operations; maintain immutable real-time audit logs of channel_id attribution in every mint transaction; perform daily automated reconciliation of recorded mint volumes against independently-tracked protocol state; isolate channels showing anomalous volume spikes pending technical review; implement transaction monitoring to flag rapid channel-switching or sudden volume concentration; require board/operations approval before executing any off-chain commission corrections or historical transaction reversals.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Unauthenticated remote code execution in Maxim AI's Bifrost LLM gateway (transports v2.0.0 and earlier) allows any netwo
Bifrost HTTP transport before version 2.0.0 exposes an unauthenticated plugin installation endpoint (POST /api/plugins)
Bifrost is a middleware package which can synchronize MySQL/MariaDB binlog data to other types of databases. Rated mediu
Bifrost is a heterogeneous middleware that synchronizes MySQL, MariaDB to Redis, MongoDB, ClickHouse, MySQL and other se
EUVD-2026-72876
GHSA-wm9v-x9j6-gf6x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB