CVE-2024-34515: image-optimizer · Deserialization of Untrusted Data
Affects image-optimizerSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 1.7.3 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.8% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade spatie/image-optimizer to 1.7.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubspatie/image-optimizerpkg:github/spatie/image-optimizerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade image-optimizer to version 1.7.3 or later as soon as the patch is available to eliminate the vulnerability.
- Until patched, implement strict input validation to prevent untrusted data from influencing file_exists() calls, especially inputs containing the phar:// protocol.
- Disable or restrict the phar:// stream wrapper in PHP configurations if not required, using php.ini settings or runtime controls.
- Employ application-layer firewalls or web application firewalls (WAFs) to detect and block requests containing suspicious phar:// usage patterns.
- Conduct code audits to identify other instances where deserialization or file protocol handling may be unsafe.
- Limit the privileges of the web server and application processes to minimize impact if exploitation occurs.
- Monitor logs for anomalous file_exists() calls or attempts to access phar:// URIs.
- Educate developers on secure deserialization practices and the risks of unsafe file protocol usage.
Description
image-optimizer before 1.7.3 allows PHAR deserialization, e.g., the phar:// protocol in arguments to file_exists().