# CVE-2026-40169: ImageMagick: Heap buffer overflow (WRITE) in the YAML and JSON encoders > A crafted image triggers a heap buffer overflow in ImageMagick's YAML and JSON encoders, causing a crash. - **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Apr 2026 - **Updated:** 14 Apr 2026 - **Also known as:** CLSA-2026-1777477457, CLSA-2026-1777478310, DEBIAN-CVE-2026-40169, GHSA-5592-p365-24xh, JLSEC-2026-1000, MINI-rr32-55gr-jpjp, UBUNTU-CVE-2026-40169 ## What is CVE-2026-40169? CVE-2026-40169 is a medium-severity memory corruption vulnerability in Imagemagick Imagemagick, published on 13 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description ImageMagick is free and open-source software used for editing and manipulating digital images. In versions below 7.1.2-19, a crafted image could result in an out of bounds heap write when writing a yaml or json output, resulting in a crash. This issue has been fixed in version 7.1.2-19. Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2026-40169? 34 open source packages ship an affected version, including Magick.NET-Q16-AnyCPU, Magick.NET-Q16-HDRI-AnyCPU and Magick.NET-Q16-HDRI-OpenMP-arm64. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Magick.NET-Q16-AnyCPU` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-AnyCPU` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-AnyCPU` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-AnyCPU` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-OpenMP-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-OpenMP-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-x86` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-HDRI-x86` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-OpenMP-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-OpenMP-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-OpenMP-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-OpenMP-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-x86` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q16-x86` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-AnyCPU` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-AnyCPU` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-OpenMP-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-OpenMP-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-OpenMP-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-OpenMP-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-arm64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-x64` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-x86` | NuGet | All versions | 14.12.0 | | `Magick.NET-Q8-x86` | NuGet | All versions | 14.12.0 | Products: Imagemagick Imagemagick. ## How do I fix CVE-2026-40169? Upgrade Magick.NET-Q16-AnyCPU to 14.12.0 or later. ## Is CVE-2026-40169 being exploited? There is no known exploitation of CVE-2026-40169 in the wild and no public exploit code. ## Other vulnerabilities in Imagemagick Imagemagick - [CVE-2019-19952](https://insights.sbomify.com/CVE-2019-19952/): Use after free in n/a (critical 9.8) - [CVE-2018-16328](https://insights.sbomify.com/CVE-2018-16328/): Null dereference in n/a (critical 9.8) - [CVE-2018-16329](https://insights.sbomify.com/CVE-2018-16329/): Null dereference in n/a (critical 9.8) - [CVE-2017-18210](https://insights.sbomify.com/CVE-2017-18210/): Null dereference in n/a (critical 9.8) - [CVE-2017-14138](https://insights.sbomify.com/CVE-2017-14138/): Denial of service in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40169 and fix it if it is affected. What it is: CVE-2026-40169 is a medium-severity memory corruption vulnerability in Imagemagick Imagemagick, published on 13 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-40169 in the wild and no public exploit code. Affected packages and fixed versions: - Magick.NET-Q16-AnyCPU (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-AnyCPU (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-AnyCPU (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-AnyCPU (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-OpenMP-arm64 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-OpenMP-arm64 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-arm64 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-arm64 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-x64 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-x64 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-x86 (NuGet): affected all versions; fixed in 14.12.0 - Magick.NET-Q16-HDRI-x86 (NuGet): affected all versions; fixed in 14.12.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40169/ (Markdown: https://insights.sbomify.com/CVE-2026-40169/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40169 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40169 - OSV: https://osv.dev/vulnerability/CVE-2026-40169 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40169/ Summaries are generated and may contain mistakes; the official description above is the record.