GHSA-vhqj-f5cj-9x8h CVE-2026-25794
ImageMagick has heap-buffer-overflow via signed integer overflow in WriteUHDRImage when writing UHDR images with large dimensions
High
NuGet
- Severity
- 8.2 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.47%
- Chance of exploitation in the next 30 days. Higher than 40.49% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
- Available
- 19 packages have a fixed version
Description
WriteUHDRImage in coders/uhdr.c uses int arithmetic to compute the pixel buffer size. When image dimensions are large, the multiplication overflows 32-bit int, causing an undersized heap allocation followed by an out-of-bounds write. This can crash the process or potentially lead to an out of bounds heap write.
==1575126==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fc382ef3820 at pc 0x5560d31f229f bp 0x7ffe865f9530 sp 0x7ffe865f9520
WRITE of size 8 at 0x7fc382ef3820 thread T0
#0 0x5560d31f229e in WriteUHDRImage coders/uhdr.c:807
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Magick.NET-Q16-AnyCPU | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-HDRI-AnyCPU | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-HDRI-OpenMP-arm64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-HDRI-OpenMP-x64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-HDRI-arm64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-HDRI-x64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-HDRI-x86 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-OpenMP-arm64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-OpenMP-x64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-OpenMP-x86 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-arm64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-x64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q16-x86 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q8-AnyCPU | < 14.10.3 |
14.10.3 |
| Magick.NET-Q8-OpenMP-arm64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q8-OpenMP-x64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q8-arm64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q8-x64 | < 14.10.3 |
14.10.3 |
| Magick.NET-Q8-x86 | < 14.10.3 |
14.10.3 |
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.10.3
- dotnet
dotnet add package Magick.NET-Q16-AnyCPU --version 14.10.3
Magick.NET-Q16-HDRI-AnyCPU NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.10.3
Magick.NET-Q16-HDRI-OpenMP-arm64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.10.3
Magick.NET-Q16-HDRI-OpenMP-x64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-x64 --version 14.10.3
Magick.NET-Q16-HDRI-arm64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.10.3
Magick.NET-Q16-HDRI-x64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.10.3
Magick.NET-Q16-HDRI-x86 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.10.3
Magick.NET-Q16-OpenMP-arm64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.10.3
Magick.NET-Q16-OpenMP-x64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-OpenMP-x64 --version 14.10.3
Magick.NET-Q16-OpenMP-x86 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-OpenMP-x86 --version 14.10.3
Magick.NET-Q16-arm64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-arm64 --version 14.10.3
Magick.NET-Q16-x64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-x64 --version 14.10.3
Magick.NET-Q16-x86 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q16-x86 --version 14.10.3
Magick.NET-Q8-AnyCPU NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q8-AnyCPU --version 14.10.3
Magick.NET-Q8-OpenMP-arm64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q8-OpenMP-arm64 --version 14.10.3
Magick.NET-Q8-OpenMP-x64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q8-OpenMP-x64 --version 14.10.3
Magick.NET-Q8-arm64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q8-arm64 --version 14.10.3
Magick.NET-Q8-x64 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q8-x64 --version 14.10.3
Magick.NET-Q8-x86 NuGet → 14.10.3
- dotnet
dotnet add package Magick.NET-Q8-x86 --version 14.10.3
Severity breakdown
CVSS 3.1 8.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- 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.
CWE-190: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How to prevent it
- Requirements: Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
- Implementation: Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range. Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
- Implementation: Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7] Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Implementation: Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.
References
Advisories
Packages
Other links
- github.com/ImageMagick/ImageMagick/security/advisories/GHSA-vhqj-f5cj-9x8h
- github.com/ImageMagick/ImageMagick/commit/ffe589df5ff8ce1433daa4ccb0d2a9fadfbe30ed
- github.com/dlemstra/Magick.NET/releases/tag/14.10.3
- access.redhat.com/security/cve/CVE-2026-25794
- bugzilla.redhat.com/show_bug.cgi
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25794.json
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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