Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
SixLabors.ImageSharp versions before 2.1.9 and from 3.0.0 before 3.1.5 are vulnerable. An attacker who can supply a specially crafted GIF file for ImageSharp to process can cause excessive memory usage in the GIF decoder. Upgrade to 2.1.9 or 3.1.5. As a workaround, call Image.Identify to check image dimensions before calling Image.Decode or Image.DecodeAsync, and enforce a limit on them.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0077, the 56th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 22 Jul 2024, 10:20 UTC Published by the maintainers as a GitHub repository advisory
- 31 Oct 2026, 15:21 UTC First seen by agentprime
- 31 Oct 2026, 15:21 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qxrv-gp6x-rc23
- OSV: GHSA-qxrv-gp6x-rc23
- github.com/SixLabors/ImageSharp/security/advisories/GHSA-qxrv-gp6x-rc23
- nvd.nist.gov/vuln/detail/CVE-2024-41132
- github.com/SixLabors/ImageSharp/pull/2759
- github.com/SixLabors/ImageSharp/pull/2764
- github.com/SixLabors/ImageSharp/pull/2770
- github.com/SixLabors/ImageSharp/commit/59de13c8cc47f2b402e2c43aa7024511d029d515
- github.com/SixLabors/ImageSharp/commit/9816ca45016c5d3859986f3c600e8934bc450a56
- github.com/SixLabors/ImageSharp/commit/b496109051cc39feee1f6cde48fca6481de17f9a
- docs.sixlabors.com/articles/imagesharp.web/processingcommands.html#securing-processing-commands
- docs.sixlabors.com/articles/imagesharp/security.html
- github.com/SixLabors/ImageSharp