Skip to main content
← Vulnerabilities

spatie url-signer URL Validation AbstractUrlSigner.php validate type conversion

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.9MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

CVE-2026-121589 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects url-signer; a fix or patch is referenced.

Published
Last modified
Published
Not listed in CISA KEV
24/100 · provisional
Fix
Fix or patch referenced
None on Exploit-DB, Metasploit or GitHub

Summary

The spatie url-signer PHP library, used to generate and validate signed URLs, is affected by this flaw in its URL validation logic. An attacker can remotely supply crafted expiration values that are converted to the wrong type, which can allow forged or improperly validated signed URLs to be accepted.

Read the original description

A weakness has been identified in spatie url-signer up to 2.1.3. Affected is the function AbstractUrlSigner::validate of the file AbstractUrlSigner.php of the component URL Validation. This manipulation of the argument expires causes incorrect type conversion. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.1.4 is able to address this issue. Patch name: 86af3355388210668f6bfbe9007bd6545d4942ad. It is recommended to upgrade the affected component.

What to do

  • Apply the patch listed under Evidence.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • spatie url-signer

    2.1.0, 2.1.1, 2.1.2, 2.1.3

Evidence 7

  1. Advisory
  2. Advisory
  3. Advisory
  4. Advisory
  5. Patch
Show all 7 sourcesShow fewer sources
  1. Patch
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121589

Is CVE-2026-121589 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121589?

url-signer: versions 2.1.0, 2.1.1, 2.1.2, 2.1.3.Source: cve.now feed data