Security: vulnerable dependency image-size (CVE-2025-71329/71330) — maintained drop-in available

[lcf2212dev]

Context

This package depends on npm image-size. Upstream is archived and the latest release (2.0.2) remains affected by:

• CVE-2025-71329 — DoS via infinite loop (JXL/HEIF/JP2 zero-size boxes)
• CVE-2025-71330 — DoS via infinite loop (ICNS zero entry length)

npm audit fix will not switch package names automatically.

Maintained drop-in

Community MIT fork with the same public API as image-size@2.0.2:

• npm: https://www.npmjs.com/package/image-size-next (image-size-next@2.1.0)
• GitHub: https://github.com/lcf2212dev/image-size-next
• Announcement: https://github.com/lcf2212dev/image-size-next/blob/main/ANNOUNCE.md

Not affiliated with the original image-size maintainer — honest community fork only.

Migration options

A — Direct dependency

npm install image-size-next

- import { imageSize } from 'image-size'
+ import { imageSize } from 'image-size-next'

fromFile: image-size/fromFile → image-size-next/fromFile

B — Force transitive resolution (npm 8.3+)

{
  "overrides": {
    "image-size": "npm:image-size-next@2.1.0"
  }
}

Ask

Happy to open a PR if that helps. Flagging this so maintainers of erisl-ncli-13 can patch on their schedule.

Thanks for maintaining open source.

[lcf2212dev]

Closing: opened by mistake due to incorrect npm repository metadata on an unrelated package. Apologies for the noise — not a security report against next.js. Correct package: https://www.npmjs.com/package/image-size-next

[nitro404]

This seems to be a bot with a new account literally spamming hundreds of repositories to promote a new supposed fork of the image-size library which he himself made. It appears that the proposed image-size-next library was just published too. Red flags everywhere on this, be warned.