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