Intel

AIKIDO-2026-42556

spatie/url-signer is vulnerable to Incorrect Type Conversion or Cast

CVE-2026-121589Published 4 days ago
November 16, 2026

69

CVE Score

Medium

Incorrect Type Conversion or Cast

Are you affected? Scan for Free

TL;DR

Before the fix, validate in spatie/url-signer passed the expires query parameter of any supplied URL straight into an integer-typed timestamp comparison, with no type or integer check and before verifying the signature. Anyone able to get an application to validate a crafted URL, typically an unauthenticated visitor clicking a signed link, could send expires[] and cause an uncaught TypeError (a 500 or denial of service); non-integer numerics like 1e10 were silently coerced. The fix requires expires and signature to be strings and validates expires as an integer with filter_var, so malformed values return false instead of crashing or coercing.

How do I fix this?

Upgrade the spatie/url-signer package to 2.1.4 or later.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and pass request URLs, such as signed links from unauthenticated clients, to validate() without first checking the expires parameter type.

Versions

2.0.0 - 2.1.3

Fixed in 2.1.4

Background info

spatie/url-signer is vulnerable to Incorrect Type Conversion or Cast in versions 2.0.0 - 2.1.3.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea