← Back
ROOT-APP-NPM-CVE-2026-33228
Vulnerability in @rootio/flatted (ROOT-APP-NPM-CVE-2026-33228)
Summary
vulnerability in @rootio/flatted (ROOT-APP-NPM-CVE-2026-33228). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `3.3.1-root.io.2, 3.3.3-root.io.2, 3.3.2-root.io.3, 3.4.1-root.io.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **ROOT-APP-NPM-CVE-2026-33228** has been found in @rootio/flatted.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade @rootio/flatted to **3.3.1-root.io.2, 3.3.3-root.io.2, 3.3.2-root.io.3, 3.4.1-root.io.1** or later.
If unsure, ask your IT team or search "@rootio/flatted ROOT-APP-NPM-CVE-2026-33228" on the vendor's site.
ROOT-APP-NPM-CVE-2026-33228 (@rootio/flatted) —
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.3.1-root.io.2, 3.3.3-root.io.2, 3.3.2-root.io.3, 3.4.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/flatted.
📍 Affected scope
@rootio/flatted — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.3.1-root.io.2, 3.3.3-root.io.2, 3.3.2-root.io.3, 3.4.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/flatted' .` 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/flatted' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@rootio/flatted` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @rootio/flatted to 3.3.1-root.io.2, 3.3.3-root.io.2, 3.3.2-root.io.3, 3.4.1-root.io.1ステージング環境で 3.3.1-root.io.2, 3.3.3-root.io.2, 3.3.2-root.io.3, 3.4.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/flatted
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.1-root.io.2"},{"fixed":"3.3.3-root.io.2"},{"fixed":"3.3.2-root.io.3"},{"fixed":"3.4.1-root.io.1"}]}]