GHSA-82mp-vp5c-9pf7 CVE-2026-55628
ImageMagick: Policy Bypass in concatenate operation due to missing checks
Medium
NuGet
- Severity
- 6.1 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.10%
- Chance of exploitation in the next 30 days. Higher than 0.76% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
- Available
- 17 packages have a fixed version
Description
The -concatenate operation is missing policy checks and that could result in both reading and writing to paths disallowed by the security policy.
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 6.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
Weakness
CWE-73: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
How to prevent it
- Architecture and Design: When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap provide this capability.
- Architecture and Design, Operation: Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- 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: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434. Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would b
- Implementation: Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59).
- Installation, Operation: Use OS-level permissions and run as a low-privileged user to limit the scope of any successful attack.
- Operation, Implementation: If you are using PHP, configure your application so that it does not use register_globals. During implementation, develop your application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
- Testing: Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
CWE-862: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
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
Advisories
Packages
Other links
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