@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.
Security
- Upgrade to patch memory corruption in /_ipx route via crafted images.
- Run npm ls ipx to confirm ipx ^2.1.2 resolves.
- Ensure patched ipx ^2.1.2 is installed for the /_ipx route.
In short
3 security2 internal
- 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 ^2.1.2, 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 for /_ipx route (GHSA-p5vf-pjf5-ggj3)
Release note
v1.11.1 is a security release.
Security release
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 ^2.1.2, 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.
Input formats are unchanged on this release line; the mitigation is the ipx upgrade itself.
Changelog
Fixes
- Security
ipx: require patched ipx for /_ipx route (GHSA-p5vf-pjf5-ggj3)
build: run nuxt-module-build prepare in prepack
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.