@nuxt/image
2.2.1 · 30 Oct 2026MIT817.3k / weekRepositoryHomepagenpmAtom feed
Summary· from the note as AI read it
Security fixUpgrade: this release fixes a security issue.
Before you upgrade
- List non-web input formats like TIFF in image.ipx.allowedInputFormats.
Security
- Upgrade to patch the /_ipx memory corruption vulnerability from crafted images.
- Run npm ls ipx to confirm ipx ^4.1.0 resolves.
- Ensure patched ipx resolves; allow extra input formats if needed.
In short
1 breaking3 security2 fixed
- Breaking
Behaviour change:
/_ipxnow only accepts common web image formats as input (JPEG, PNG, WebP, GIF, SVG, AVIF, HEIC) and responds403to anything else, before decoding it. If you transform other formats (for example TIFF), list them with the newimage.ipx.allowedInputFormatsoption. For sources you do not fully trust, also considerimage.ipx.restrictDecoders, which blocks the decoders of every other format for the whole process. - Security
This release fixes a vulnerability in the
/_ipximage transformation route.ipxwas affected by an integer overflow when decoding a multi-page image, so a crafted source image could corrupt memory in the server process with a single unauthenticated request (GHSA-qf89-6xm4-66wm; our advisory for the@nuxt/imageside is GHSA-p5vf-pjf5-ggj3). Sites where an attacker cannot control any image source are not affected. - Security
@nuxt/imagenow requiresipx ^4.1.0, which rejects oversized multi-page images with a400before decoding them.ipxis an optional dependency, so after upgrading runnpm ls ipxto confirm a patched version resolves. - Security
ipx: require patched ipx and restrict input formats for /_ipx route (GHSA-p5vf-pjf5-ggj3)
Release note
v2.2.1 is a security release.
Security
This release fixes a vulnerability in the /_ipx image transformation route. ipx was affected by an integer overflow when decoding a multi-page image, so a crafted source image could corrupt memory in the server process with a single unauthenticated request (GHSA-qf89-6xm4-66wm; our advisory for the @nuxt/image side is GHSA-p5vf-pjf5-ggj3). Sites where an attacker cannot control any image source are not affected.
@nuxt/image now requires ipx ^4.1.0, which rejects oversized multi-page images with a 400 before decoding them. ipx is an optional dependency, so after upgrading run npm ls ipx to confirm a patched version resolves.
Behaviour change: /_ipx now only accepts common web image formats as input (JPEG, PNG, WebP, GIF, SVG, AVIF, HEIC) and responds 403 to anything else, before decoding it. If you transform other formats (for example TIFF), list them with the new image.ipx.allowedInputFormats option. For sources you do not fully trust, also consider image.ipx.restrictDecoders, which blocks the decoders of every other format for the whole process.
Changelog
Fixes
- Security
ipx: require patched ipx and restrict input formats for /_ipx route (GHSA-p5vf-pjf5-ggj3)
ipx: use IPXFetchHandler so
srvx/nodeis not required at runtimeipx: import
NitroRuntimeConfigfromnitropack/types
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.