Skip to content

GHSA-jvgr-9ph5-m8v4 CVE-2026-40183

ImageMagick has a heap buffer overflow when encoding JXL image with a 16-bit float

Medium NuGet
Severity
5.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.19%
Chance of exploitation in the next 30 days. Higher than 8.39% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-122 Heap-based Buffer Overflow
Fix
Available
17 packages have a fixed version

Description

The JXL encoder has an heap write overflow when a user specifies that the image should be encoded as 16 bit floats.

Affected versions

NuGet

PackageVulnerableFixed in
Magick.NET-Q16-AnyCPU
< 14.12.0
14.12.0
Magick.NET-Q16-HDRI-AnyCPU
< 14.12.0
14.12.0
Magick.NET-Q16-HDRI-OpenMP-arm64
< 14.12.0
14.12.0
Magick.NET-Q16-HDRI-arm64
< 14.12.0
14.12.0
Magick.NET-Q16-HDRI-x64
< 14.12.0
14.12.0
Magick.NET-Q16-HDRI-x86
< 14.12.0
14.12.0
Magick.NET-Q16-OpenMP-arm64
< 14.12.0
14.12.0
Magick.NET-Q16-OpenMP-x64
< 14.12.0
14.12.0
Magick.NET-Q16-arm64
< 14.12.0
14.12.0
Magick.NET-Q16-x64
< 14.12.0
14.12.0
Magick.NET-Q16-x86
< 14.12.0
14.12.0
Magick.NET-Q8-AnyCPU
< 14.12.0
14.12.0
Magick.NET-Q8-OpenMP-arm64
< 14.12.0
14.12.0
Magick.NET-Q8-OpenMP-x64
< 14.12.0
14.12.0
Magick.NET-Q8-arm64
< 14.12.0
14.12.0
Magick.NET-Q8-x64
< 14.12.0
14.12.0
Magick.NET-Q8-x86
< 14.12.0
14.12.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.12.0

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Magick.NET-Q16-arm64 NuGet → 14.12.0

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

Magick.NET-Q16-x64 NuGet → 14.12.0

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

Magick.NET-Q16-x86 NuGet → 14.12.0

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

Magick.NET-Q8-AnyCPU NuGet → 14.12.0

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

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

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

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

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

Magick.NET-Q8-arm64 NuGet → 14.12.0

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

Magick.NET-Q8-x64 NuGet → 14.12.0

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

Magick.NET-Q8-x86 NuGet → 14.12.0

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

Severity breakdown

CVSS 3.1 5.5

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

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

Weakness

CWE-122: Heap-based Buffer Overflow

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How to prevent it
  • Pre-design: Use a language or compiler that performs automatic bounds checking.
  • Architecture and Design: Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Operation, Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Operation, Build and Compilation: Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
  • Implementation: Implement and perform bounds checking on input.
  • Implementation: Do not use dangerous functions such as gets. Look for their safe equivalent, which checks for the boundary.
  • Operation: Use OS-level preventative functionality. This is not a complete solution, but it provides some defense in depth.

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