Laravel Local Disk: Expired Temporary URLs Can Stay Valid

Published as "Laravel Framework: Temporary Signed URL Path Confusion"

medium Laravel Laravel framework · Last reviewed Nov 7, 2026

CVE: No CVE assigned
GHSA: GHSA-crmm-hgp2-wgrp
Packagist: PKSA-m5cs-t1y6-qpcs
Reported: Jun 17, 2026

Can let expired temporary signed URLs keep working, or point to a different file, in Laravel apps that serve the local disk with temporary URLs.

Affected and fixed versions

In laravel/framework. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
13.0.0 – 13.11.x	13.12.0	Supported
Up to 12.61.0	12.61.1	Supported

Upgrade

Run the line for the branch you are on.

composer require laravel/framework:^13.12.0
composer require laravel/framework:^12.61.1

What this means

On Laravel's local filesystem driver, a temporary signed URL could be read differently by the server than when it was signed. An expired link could keep working indefinitely, or a link could open a different file than the one that was signed. Temporary upload URLs could write to an unintended place.

The storage path wasn't URL-encoded inside the signed URL. Characters such as ?, & and # in a file's path could cut the path short and change how the URL's query string, including its expires value, was read. See the Laravel advisory and the fixes for 13.x and 12.x.

Who is affected

Apps that call Storage::temporaryUrl() or Storage::temporaryUploadUrl() on a disk that uses the local driver. The risk is highest when stored file paths can contain ?, & or #, for example when paths are built from the names of files users upload.

The advisory covers only the local filesystem driver. Temporary URLs from S3 and other drivers are not part of it.

What to do

Update laravel/framework to 12.61.1 on 12.x or 13.12.0 on 13.x.

Reported by teebow1e and zxcvbbq.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Laravel Local Disk: Expired Temporary URLs Can Stay Valid (GHSA-crmm-hgp2-wgrp)
Details: https://phpnews.net/security/laravel/ghsa-crmm-hgp2-wgrp

Affected versions, as Composer constraints:
- laravel/framework: <12.61.1|>=13.0.0,<13.12.0

Fixed releases on branches that still get security fixes:
- 13.0.0 – 13.11.x: update to 13.12.0
- Up to 12.61.0: update to 12.61.1

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/laravel/ghsa-crmm-hgp2-wgrp and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

GitHub advisory GHSA-crmm-hgp2-wgrp →

← All Laravel advisories