Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

image-size Denial of Service via Infinite Loop during Image Processing

CVE-2025-71319GHSA-m5qc-5hw7-8vg7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (image-size 2.0.2, 1.2.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm image-size

    Affected
    >= 1.1.0, < 1.2.1>= 2.0.0, < 2.0.2
    Fixed in
    2.0.2, 1.2.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-71319: 0.73% estimated exploitation activity in the next 30 days; percentile 54.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary image-size is vulnerable to a Denial of Service vulnerability when processing specially crafted images. The issue occurs because of an infine loop in findBox when processing certain images with a box with size 0. Details If the first bytes of the input does not match any bytes in firstBytes, then the package tries to validate the image using other handlers: Some handlers that call findBox to validate or calculate the image size are jxl, heif and jp2. JXL handler calls findBox inside validate. To reach the findBox call, the value at position 4:8 should be 'JXL ' findBox can lead to an infinite loop because the value of box.size is 0, thus the offset variable is not updated. Below relevant code with comments (using one of the PAYLOAD below as example): A similar issue occurs for HEIF and JP2 handlers: - https://github.com/image-size/image-size/blob/v1.2.0/lib/types/heif.ts - https://github.com/image-size/image-size/blob/v1.2.0/lib/types/jp2.ts PoC Usage: - poc for…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-m5qc-5hw7-8vg7

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-m5qc-5hw7-8vg7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-71319

Advisory: image-size Denial of Service via Infinite Loop during Image Processing
IDs: CVE-2025-71319, GHSA-m5qc-5hw7-8vg7
Record: https://patchnext.com/advisories/cve-2025-71319 (revision 3, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: image-size 2.0.2, 1.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm image-size: affected >= 1.1.0, < 1.2.1; >= 2.0.0, < 2.0.2; fixed in 2.0.2, 1.2.1

## Suggested inspection (read-only)
- `npm ls image-size --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on image-size.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m5qc-5hw7-8vg7 (OSV record GHSA-m5qc-5hw7-8vg7 lists affected ranges: npm image-size >=1.1.0 =2.0.0 <2.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-m5qc-5hw7-8vg7 (GitHub-reviewed advisory GHSA-m5qc-5hw7-8vg7 lists affected ranges: npm image-size >=1.1.0 =2.0.0 <2.0.2)

Commands are suggestions: review each one before running it.

Loading voting…