CVE-2025-54387: IPX is an image optimizer powered by sharp and svgo

Q: How do I fix CVE-2025-54387?

ipx: upgrade to 1.3.2, 2.1.1, 3.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-54387 being exploited?

CVE-2025-54387 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-54387 affect?

CVE-2025-54387 affects ipx. Severity is critical (CVSS 9.8). 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 wh

Q: How urgent is CVE-2025-54387?

Priority 58/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-54387 is a critical-severity flaw (CVSS 9.8) affecting ipx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-22
Published	2025-08-05
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: unjs

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-08-05 01:15 UTCPublished CVE record published
2026-06-17 09:39 UTCUpdated Record last modified

unjs ipx UPGRADE

Affected: < 1.3.2 · >= 2.0.0 and < 2.1.1 · >= 3.0.0 and < 3.1.1

Fixed in: 1.3.2, 2.1.1, 3.1.1

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls ipx

2. UPGRADE to 1.3.2

npm install ipx@">=1.3.2"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0

npm view ipx versions npm install ipx@"<2.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-54387?

ipx: upgrade to 1.3.2, 2.1.1, 3.1.1. Exact commands for each OS are on this page.

Is CVE-2025-54387 being exploited?

CVE-2025-54387 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-54387 affect?

CVE-2025-54387 affects ipx. Severity is critical (CVSS 9.8). 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 wh

How urgent is CVE-2025-54387?

Priority 58/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs