CVE-2025-54387: unjs ipx · Path Traversal
Affects unjs ipxSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.3.2 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.3.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2025
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 unjs ipx to 1.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| unjs ipx | Affected
| Fixed in
|
AI-suggested
European organizations should prioritize upgrading ipx to the fixed versions: 1.3.2, 2.1.1, or 3.1.1 depending on their current version. If immediate upgrade is not feasible, implement strict input validation and sanitization on all file path inputs to ensure they cannot be manipulated to traverse directories. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block path traversal attempts targeting ipx endpoints. Restrict file system permissions for the ipx process to limit access only to necessary directories, minimizing the impact of any traversal attempts. Conduct thorough code reviews and penetration testing focusing on file path handling in image optimization workflows. Monitor logs for suspicious path access patterns indicative of exploitation attempts. Finally, maintain an inventory of all applications and services using ipx to ensure comprehensive patching and risk assessment.
Description
IPX is an image optimizer powered by sharp and svgo. In versions 1.3.1 and below, 2.0.0-0 through 2.1.0, and 3.0.0 through 3.1.0, the approach used to check whether a path is within allowed directories is vulnerable to path prefix bypass when the allowed directories do not end with a path separator. This occurs because the check relies on a raw string prefix comparison. This is fixed in versions 1.3.2, 2.1.1 and 3.1.1.
References
- github.com/unjs/ipx/security/advisories/GHSA-mm3p-j368-7jcr (opens in a new tab)
- github.com/unjs/ipx/commit/81693ddbfc062cc922e4e2406e8427ab4e3ad214 (opens in a new tab)
- github.com/unjs/ipx/releases/tag/v1.3.2 (opens in a new tab)
- github.com/unjs/ipx/releases/tag/v2.1.1 (opens in a new tab)
- github.com/unjs/ipx/releases/tag/v3.1.1 (opens in a new tab)