← Back
CVE-2026-48067 medium CVSS 6.5

Vulnerability in filament/tables (CVE-2026-48067)

Summary

vulnerability in filament/tables (CVE-2026-48067). Data can be tampered with by attackers. Exploitable via ``Select``. Mitigation: upgrade to `3.3.51` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-48067** has been found in filament/tables. Attackers can target a specific entry point like ``Select`` over the network to misuse the product. Data can be tampered with by attackers. CVSS score: 6.5/10. What to do: upgrade filament/tables to **3.3.51** or later. If unsure, ask your IT team or search "filament/tables CVE-2026-48067" on the vendor's site.
CVE-2026-48067 (filament/tables) — CWE-639 / CVSS v3 6.5 Attack vector: remote (network-reachable) / no user interaction Attack surface: `Select` / `AttachAction` / `AssociateAction` Patched: `3.3.51` — 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** (CWE-639) exists in filament/tables. Attackers reach the vulnerable code path via ``Select`` without authentication.
📍 Affected scope
filament/tables — . Attack surface: `Select` / `AttachAction` / `AssociateAction`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **3.3.51**.
🛡️ 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 'filament/tables' .` 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

  1. 1
    Identify exposure identify
    grep -r 'filament/tables' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `filament/tables` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade filament/tables to 3.3.51

    ステージング環境で 3.3.51 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer filament/tables
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.51"}]}]
composer filament/actions
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.6.4"}]}]
Packagist filament/tables
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.3.51"}]}]
Packagist filament/actions
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.6.4"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →