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.
CVE-2026-86840
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- 72(Attend)EG Risk 72/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
September 8, 2026
Last Modified
September 10, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Bifrost Protocol — Unvalidated channel_id Allows Arbitrary Commission Share Inflation · GitHub
https://gist.github.com/prasanna8585/ffd112b1a125ca4c5533fdce45ef57c1Vendor Advisories for CVE-2026-86840(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 55× in last 7d / 83× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 03:46 UTCGHSA enrichment
- 2026-09-19 23:50 UTCGHSA enrichment
- 2026-09-19 19:55 UTCGHSA enrichment
- 2026-09-19 15:59 UTCEG score recompute
- 2026-09-19 15:59 UTCGHSA enrichment
- 2026-09-19 11:58 UTCGHSA enrichment
- 2026-09-19 08:02 UTCGHSA enrichment
- 2026-09-19 04:06 UTCGHSA enrichment
- 2026-09-19 00:11 UTCGHSA enrichment
- 2026-09-18 20:15 UTCEG score recompute
- 2026-09-18 20:15 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:14 UTCGHSA enrichment
- 2026-09-18 12:03 UTCGHSA enrichment
- 2026-09-18 08:07 UTCGHSA enrichment
- 2026-09-18 04:11 UTCGHSA enrichment
- 2026-09-18 00:15 UTCGHSA enrichment
- 2026-09-17 20:19 UTCEG score recompute
- 2026-09-17 20:19 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 14:44 UTCGHSA enrichment
- 2026-09-17 10:48 UTCGHSA enrichment
- 2026-09-17 06:52 UTCGHSA enrichment
- 2026-09-17 02:57 UTCGHSA enrichment
- 2026-09-16 22:27 UTCGHSA enrichment
Show 58 moreShow fewer
- 2026-09-16 18:17 UTCEG score recompute
- 2026-09-16 18:17 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 13:57 UTCGHSA enrichment
- 2026-09-16 10:01 UTCGHSA enrichment
- 2026-09-16 06:05 UTCEG score recompute
- 2026-09-16 06:05 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 02:09 UTCGHSA enrichment
- 2026-09-15 22:13 UTCGHSA enrichment
- 2026-09-15 18:17 UTCGHSA enrichment
- 2026-09-15 14:00 UTCGHSA enrichment
- 2026-09-15 10:04 UTCGHSA enrichment
- 2026-09-15 06:07 UTCEG score recompute
- 2026-09-15 06:07 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 02:11 UTCGHSA enrichment
- 2026-09-14 22:16 UTCGHSA enrichment
- 2026-09-14 18:20 UTCGHSA enrichment
- 2026-09-14 14:18 UTCGHSA enrichment
- 2026-09-14 10:22 UTCGHSA enrichment
- 2026-09-14 06:26 UTCGHSA enrichment
- 2026-09-14 02:31 UTCGHSA enrichment
- 2026-09-13 22:35 UTCGHSA enrichment
- 2026-09-13 18:40 UTCEG score recompute
- 2026-09-13 18:40 UTCGHSA enrichment
- 2026-09-13 14:44 UTCGHSA enrichment
- 2026-09-13 10:46 UTCGHSA enrichment
- 2026-09-13 06:50 UTCGHSA enrichment
- 2026-09-13 02:46 UTCGHSA enrichment
- 2026-09-12 22:51 UTCGHSA enrichment
- 2026-09-12 18:55 UTCEG score recompute
- 2026-09-12 18:55 UTCGHSA enrichment
- 2026-09-12 15:00 UTCGHSA enrichment
- 2026-09-12 11:04 UTCGHSA enrichment
- 2026-09-12 07:05 UTCGHSA enrichment
- 2026-09-12 03:09 UTCGHSA enrichment
- 2026-09-11 23:13 UTCGHSA enrichment
- 2026-09-11 19:01 UTCGHSA enrichment
- 2026-09-11 15:00 UTCEG score recompute
- 2026-09-11 15:00 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 11:04 UTCEG score recompute
- 2026-09-11 11:04 UTCGHSA enrichment
- 2026-09-11 07:08 UTCGHSA enrichment
- 2026-09-11 03:13 UTCGHSA enrichment
- 2026-09-10 23:17 UTCEG score recompute
- 2026-09-10 23:17 UTCGHSA enrichment
- 2026-09-10 19:21 UTCGHSA enrichment
- 2026-09-10 18:35 UTCEG score recompute▲ 9.10
- 2026-09-10 18:35 UTCGHSA enrichment
- 2026-09-10 18:35 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
- 2026-09-08 19:49 UTCGHSA enrichment
- 2026-09-08 16:28 UTCNVD update
- 2026-09-08 15:37 UTCEG score recompute
- 2026-09-08 15:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639 · CWE-862
Frequently asked(5)
What is CVE-2026-86840?
When was CVE-2026-86840 disclosed?
Is CVE-2026-86840 actively exploited?
What is the CVSS score of CVE-2026-86840?
How do I remediate CVE-2026-86840?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-86840
Is Your Infrastructure Affected by CVE-2026-86840?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.