Skip to content

GHSA-qhmf-7fc4-8q3h CVE-2026-55595

ImageMagick: Infinite Loop in connected-components when providing invalid arguments

Medium NuGet
Severity
4.7 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.09%
Chance of exploitation in the next 30 days. Higher than 0.43% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
Fix
Available
17 packages have a fixed version

Description

When providing invalid arguments to the connected-components option an infinite loop will occur.

Affected versions

NuGet

PackageVulnerableFixed in
Magick.NET-Q16-AnyCPU
< 14.15.0
14.15.0
Magick.NET-Q16-HDRI-AnyCPU
< 14.15.0
14.15.0
Magick.NET-Q16-HDRI-OpenMP-arm64
< 14.15.0
14.15.0
Magick.NET-Q16-HDRI-arm64
< 14.15.0
14.15.0
Magick.NET-Q16-HDRI-x64
< 14.15.0
14.15.0
Magick.NET-Q16-HDRI-x86
< 14.15.0
14.15.0
Magick.NET-Q16-OpenMP-arm64
< 14.15.0
14.15.0
Magick.NET-Q16-OpenMP-x64
< 14.15.0
14.15.0
Magick.NET-Q16-arm64
< 14.15.0
14.15.0
Magick.NET-Q16-x64
< 14.15.0
14.15.0
Magick.NET-Q16-x86
< 14.15.0
14.15.0
Magick.NET-Q8-AnyCPU
< 14.15.0
14.15.0
Magick.NET-Q8-OpenMP-arm64
< 14.15.0
14.15.0
Magick.NET-Q8-OpenMP-x64
< 14.15.0
14.15.0
Magick.NET-Q8-arm64
< 14.15.0
14.15.0
Magick.NET-Q8-x64
< 14.15.0
14.15.0
Magick.NET-Q8-x86
< 14.15.0
14.15.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Magick.NET-Q16-AnyCPU NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-AnyCPU --version 14.15.0

Magick.NET-Q16-HDRI-AnyCPU NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.15.0

Magick.NET-Q16-HDRI-OpenMP-arm64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.15.0

Magick.NET-Q16-HDRI-arm64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.15.0

Magick.NET-Q16-HDRI-x64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.15.0

Magick.NET-Q16-HDRI-x86 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.15.0

Magick.NET-Q16-OpenMP-arm64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.15.0

Magick.NET-Q16-OpenMP-x64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-OpenMP-x64 --version 14.15.0

Magick.NET-Q16-arm64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-arm64 --version 14.15.0

Magick.NET-Q16-x64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-x64 --version 14.15.0

Magick.NET-Q16-x86 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q16-x86 --version 14.15.0

Magick.NET-Q8-AnyCPU NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q8-AnyCPU --version 14.15.0

Magick.NET-Q8-OpenMP-arm64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q8-OpenMP-arm64 --version 14.15.0

Magick.NET-Q8-OpenMP-x64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q8-OpenMP-x64 --version 14.15.0

Magick.NET-Q8-arm64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q8-arm64 --version 14.15.0

Magick.NET-Q8-x64 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q8-x64 --version 14.15.0

Magick.NET-Q8-x86 NuGet → 14.15.0

dotnet
dotnet add package Magick.NET-Q8-x86 --version 14.15.0

Severity breakdown

CVSS 3.1 4.7

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-400: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How to prevent it
  • Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
  • Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
  • Implementation: Ensure that all failures in resource allocation place the system into a safe posture.

CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-j7hp-h8jx-5ppr
libwebp: OOB write in BuildHuffmanTable
High Known exploited Also affects magick.net-q16-anycpu
GHSA-cvhv-g4rq-3hmw
ImageMagick: Memory Leak when providing invalid options to the cli
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-h22j-f9xw-xjjm
ImageMagick: Integer Overflow in JNX decoder causes heap buffer over-write when processing extremly large files on 32-bit builds
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-422r-8c97-xcg4
ImageMagick: Heap Buffer Over-Write in fx operation
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-f5m7-cqgw-8hm7
ImageMagick: Heap Buffer Over-Write in morphology operation when an invalid kernel is provided
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-hc76-7mpc-qjqh
ImageMagick: Code injection in HTML encoder due to incomplete fix of CVE-2026-25797
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-56m6-8q75-f2rw
ImageMagick: Policy Bypass due to an incomplete fix of CVE-2026-49219
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-h5r4-w88w-7ccr
ImageMagick: Memory Leak in TIFF encoder when invalid tiff:tile-geometry is specified
Low Also affects Magick.NET-Q16-AnyCPU
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor