# CVE-2026-48067: Filament: Inconsistent scope enforcement for AttachAction and AssociateAction Select fields

> Attackers can bypass scope restrictions in Filament Attach/Associate actions to modify out-of-scope records by tampering with Livewire state.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-7q3w-xqjw-g3cr

## What is CVE-2026-48067?

CVE-2026-48067 is a medium-severity missing authorization vulnerability in filamentphp filament, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-48067?

6 open source packages ship an affected version, including filament/actions and filament/tables.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/actions` | Packagist | From 4.0.0 | 4.11.4 |
| `filament/actions` | Packagist | From 4.0.0 | 4.11.4 |
| `filament/actions` | Packagist | From 5.0.0 | 5.6.4 |
| `filament/actions` | Packagist | From 5.0.0 | 5.6.4 |
| `filament/tables` | Packagist | From 3.0.0 | 3.3.51 |
| `filament/tables` | Packagist | From 3.0.0 | 3.3.51 |

## How do I fix CVE-2026-48067?

Upgrade filament/actions to a fixed version for your release line: 4.11.4 or 5.6.4.

## Is CVE-2026-48067 being exploited?

There is no known exploitation of CVE-2026-48067 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48067 and fix it if it is affected.

What it is: CVE-2026-48067 is a medium-severity missing authorization vulnerability in filamentphp filament, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48067 in the wild and no public exploit code.

Affected packages and fixed versions:
- filament/actions (Packagist): affected from 4.0.0; fixed in 4.11.4
- filament/actions (Packagist): affected from 4.0.0; fixed in 4.11.4
- filament/actions (Packagist): affected from 5.0.0; fixed in 5.6.4
- filament/actions (Packagist): affected from 5.0.0; fixed in 5.6.4
- filament/tables (Packagist): affected from 3.0.0; fixed in 3.3.51
- filament/tables (Packagist): affected from 3.0.0; fixed in 3.3.51

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48067/ (Markdown: https://insights.sbomify.com/CVE-2026-48067/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48067
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48067
- OSV: https://osv.dev/vulnerability/CVE-2026-48067

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48067/
Summaries are generated and may contain mistakes; the official description above is the record.