Categories
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.

Original description

The description as published by the source.

Filament is a collection of full-stack components for accelerated Laravel development. From filament/actions 4.0.0 until 4.11.4 and 5.6.4 and from filament/tables 3.0.0 until 3.3.51, the recordSelectOptionsQuery() method may be used to scope the options available in the Select field for AttachAction and AssociateAction. However, the built-in validation rule for these fields did not apply the same scope. As a result, a user who can trigger these actions could tamper with the Livewire component's state and submit an out-of-scope value. This vulnerability is fixed in filament/actions 4.11.4 and 5.6.4 and filament/tables 3.3.51.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

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. 2
    Apply patch patch
    Upgrade filament/tables to 3.3.51

    ステージング環境で 3.3.51 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

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

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details