Skip to main content
CVE-2026-134165VulnerabilityPublished

probe-image-size before 7.5.0 contains an unbounded memory allocation vulnerability in lib/parse_stream/avif.js that

Affects probe-image-sizeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-134165· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 7.5.0 when convenient.

Data as of 21 Nov 2026, 01:47 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 7.5.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade probe-image-size to 7.5.0.

Affected software

ProductAffectedFixed in
npmprobe-image-sizepkg:npm/probe-image-sizeOther threatsAffected
  • <7.5.0
Fixed in
  • 7.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in probe-image-size version 7.5.0 and later. Users should upgrade to version 7.5.0 or newer to remediate this vulnerability. No other mitigation or workaround is indicated.

Description

probe-image-size versions before 7.5.0 have an unbounded memory allocation vulnerability in the lib/parse_stream/avif.js component. This flaw allows remote attackers to cause a denial of service by supplying an AVIF stream or URL with attacker-declared ftyp or meta box sizes that are excessively large. The parser buffers all received bytes based on these declared sizes, leading to memory exhaustion.

References

Community reviews

Loading reviews…