GHSA-vfxr-r8f8-gfmp: Sanctum guard can resolve the lowest-ID user when evaluated inside an eager-loaded Eloquent relation definition
- Published:
- Fetched:
- Updated:
- Affects:
- laravel laravel/framework
https://github.com/laravel/framework/security/advisories/GHSA-vfxr-r8f8-gfmp ↗
Sanctum guard can resolve the lowest-ID user when evaluated inside an eager-loaded Eloquent relation definition ### Impact When an authenticated user is first resolved while Eloquent is initializing an eager-loaded relation, Eloquent's relation constraints are temporarily disabled. A lazy key-constrained lookup made during that window, such as Sanctum's token owner lookup, runs without its key restriction. The guard can then return the lowest-ID user (often an administrator) instead of the token's owner. This affects applications that call the guard inside a relation definition used with eager loading, for example in optional-authentication routes. A low-privilege token could then read that user's data, and the wrong user remains cached for the rest of the request. Routes where authentication middleware resolves the user first were not affected in testing. ### Patches The fix for the 12.x branch has been merged in https://github.com/laravel/framework/pull/62483, which keeps constraints enabled when nested relation attributes are resolved during eager-load relation initialization. ### Workarounds Avoid resolving the authenticated user inside relation definitions. Resolve the user ID beforehand and pass it explicitly through an eager-load constraint closure. Affected packages: composer:laravel/framework Patched: laravel/framework >=12.73.0