GHSA-56m6-8q75-f2rw
ImageMagick: Policy Bypass due to an incomplete fix of CVE-2026-49219
Medium
NuGet
- Severity
- 4.7 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- —
- No score published
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
- CWE-59 Improper Link Resolution Before File Access ('Link Following')
- CWE-863 Incorrect Authorization
- Fix
- Available
- 17 packages have a fixed version
Description
An incomplete fix of CVE-2026-49219 could result in a policy bypass.
Affected versions
NuGet
| Package | Vulnerable | Fixed 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:L/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
How to prevent it
- Implementation: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
- Implementation: When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
- Architecture and Design: Limit the interleaving of operations on files from multiple processes.
- Implementation, Architecture and Design: If you cannot perform operations atomically and you must share access to the resource between multiple processes or threads, then try to limit the amount of time (CPU cycles) between the check and use of the resource. This will not fix the problem, but it could make it more difficult for an attack to succeed.
- Implementation: Recheck the resource after the use call to verify that the action was taken appropriately.
- Architecture and Design: Ensure that some environmental locking mechanism can be used to protect resources effectively.
- Implementation: Ensure that locking occurs before the check, as opposed to afterwards, such that the resource, as checked, is the same as it is when in use.
CWE-59: Improper Link Resolution Before File Access ('Link Following')
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
How to prevent it
- Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.
CWE-863: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
- 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. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Packages
Other links
Timeline
- Published
- Last updated by the source
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-h5r4-w88w-7ccr ImageMagick: Memory Leak in TIFF encoder when invalid tiff:tile-geometry is specified | Low | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-h58x-r7f7-rh84 ImageMagick: Memory Leak in ICON decoder when allocation fails | Medium | 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