Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.2

Laravel Framework: Temporary Signed URL Path Confusion

GHSA-crmm-hgp2-wgrp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (laravel/framework 13.12.0, 12.61.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist laravel/framework

    Affected
    >= 13.0.0, < 13.12.0< 12.61.1
    Fixed in
    13.12.0, 12.61.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.2 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

A vulnerability in Laravel's local filesystem driver allows temporary signed URLs to be parsed ambiguously, potentially misrouting requests and bypassing expiration enforcement. Under certain conditions, a generated temporary signed URL can be interpreted differently by the server than intended at signing time. This may cause requests to resolve to an unintended resource, and can prevent expiration from being enforced, allowing expired URLs to remain valid indefinitely. Impact - Expired temporary URLs may continue to be accepted - Requests may resolve to a different resource than the one that was signed - The upload variant may allow writes to reach an unintended destination

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-crmm-hgp2-wgrp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-crmm-hgp2-wgrp

Advisory: Laravel Framework: Temporary Signed URL Path Confusion
IDs: GHSA-crmm-hgp2-wgrp
Record: https://patchnext.com/advisories/ghsa-crmm-hgp2-wgrp (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: laravel/framework 13.12.0, 12.61.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist laravel/framework: affected >= 13.0.0, < 13.12.0; < 12.61.1; fixed in 13.12.0, 12.61.1

## Suggested inspection (read-only)
- Packagist laravel/framework: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on laravel/framework.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-crmm-hgp2-wgrp (GitHub-reviewed advisory GHSA-crmm-hgp2-wgrp lists affected ranges: Packagist laravel/framework >=13.0.0 =0 <12.61.1)

Commands are suggestions: review each one before running it.

Loading voting…