GHSA-rw6c-xp26-225v CVE-2026-25797
ImageMagick: Code Injection via PostScript header in ps coders
Medium
NuGet
- Severity
- 5.7 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.28%
- Chance of exploitation in the next 30 days. Higher than 20.35% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-94 Improper Control of Generation of Code ('Code Injection')
- Fix
- Available
- 18 packages have a fixed version
Description
The ps encoders, responsible for writing PostScript files, fails to sanitize the input before writing it into the PostScript header. An attacker can provide a malicious file and inject arbitrary PostScript code. When the resulting file is processed by a printer or a viewer (like Ghostscript), the injected code is interpreted and executed.
The html encoder does not properly escape strings that are written to in the html document. An attacker can provide a malicious file and injection arbitrary html code.
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-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-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 5.7
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
Weakness
CWE-94: Improper Control of Generation of Code ('Code Injection')
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How to prevent it
- Architecture and Design: Refactor your program so that you do not have to dynamically generate code.
- Architecture and Design: 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 which code can be executed by your product. 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.
- 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. To reduce the likelihood of code injection, use stringent allowlists that limit which constructs are allowed. If you are dynamically constructing code that invokes a function, then verifying that the input is alphanumeric might be insufficient. An attacker might still be able to reference a dangerous function that you did not intend to allow, such as system(), exec(), or exit().
- Testing: Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
- Operation: Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
- Operation: Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
- Implementation: For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures [REF-1372], so the python documentation discourages use of ast.literal_eval() on untrusted data [REF-1373].
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