← Back
ROOT-APP-NPM-CVE-2026-2739
Vulnerability in @rootio/bn.js (ROOT-APP-NPM-CVE-2026-2739)
Summary
vulnerability in @rootio/bn.js (ROOT-APP-NPM-CVE-2026-2739). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `4.12.2-root.io.1, 4.11.9-root.io.1, 4.12.2-root.io.2, 4.11.9-root.io.2, 4.12.1-root.io.1, 5.2.1-root.io.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **ROOT-APP-NPM-CVE-2026-2739** has been found in @rootio/bn.js.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @rootio/bn.js to **4.12.2-root.io.1, 4.11.9-root.io.1, 4.12.2-root.io.2, 4.11.9-root.io.2, 4.12.1-root.io.1, 5.2.1-root.io.1** or later.
If unsure, ask your IT team or search "@rootio/bn.js ROOT-APP-NPM-CVE-2026-2739" on the vendor's site.
ROOT-APP-NPM-CVE-2026-2739 (@rootio/bn.js) —
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `4.12.2-root.io.1, 4.11.9-root.io.1, 4.12.2-root.io.2, 4.11.9-root.io.2, 4.12.1-root.io.1, 5.2.1-root.io.1` — 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** (unclassified) exists in @rootio/bn.js.
📍 Affected scope
@rootio/bn.js — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.12.2-root.io.1, 4.11.9-root.io.1, 4.12.2-root.io.2, 4.11.9-root.io.2, 4.12.1-root.io.1, 5.2.1-root.io.1**.
🛡️ 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 '@rootio/bn.js' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@rootio/bn.js' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@rootio/bn.js` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @rootio/bn.js to 4.12.2-root.io.1, 4.11.9-root.io.1, 4.12.2-root.io.2, 4.11.9-root.io.2, 4.12.1-root.io.1, 5.2.1-root.io.1ステージング環境で 4.12.2-root.io.1, 4.11.9-root.io.1, 4.12.2-root.io.2, 4.11.9-root.io.2, 4.12.1-root.io.1, 5.2.1-root.io.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Root:npm
@rootio/bn.js
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.2-root.io.1"},{"fixed":"4.11.9-root.io.1"},{"fixed":"4.12.2-root.io.2"},{"fixed":"4.11.9-root.io.2"},{"fixed":"4.12.1-root.io.1"},{"fixed":"5.2.1-root.io.1"}]}]
Root:npm
bn.js
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.2-aikido.2"},{"fixed":"4.11.9-aikido.2"},{"fixed":"4.12.1-aikido.1"},{"fixed":"5.2.1-aikido.1"}]}]