Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
SixLabors.ImageSharp versions before 2.1.8 and from 3.0.0 before 3.1.4 are vulnerable. An attacker who can supply a specially crafted image file for processing can cause excessive memory usage in the image decoders, leading to denial of service by exhausting process memory. Upgrade to version 2.1.8 or 3.1.4. Before calling Image.Decode or Image.DecodeAsync, call Image.Identify to check image dimensions and enforce a size limit.
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.0063, the 50th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 15 Apr 2024, 10:39 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-g85r-6x2q-45w7
- OSV: GHSA-g85r-6x2q-45w7
- github.com/SixLabors/ImageSharp/security/advisories/GHSA-g85r-6x2q-45w7
- nvd.nist.gov/vuln/detail/CVE-2024-32035
- github.com/SixLabors/ImageSharp/commit/b6b08ac3e7cea8da5ac1e90f7c0b67dd254535c3
- github.com/SixLabors/ImageSharp/commit/f21d64188e59ae9464ff462056a5e29d8e618b27
- docs.sixlabors.com/articles/imagesharp.web/processingcommands.html#securing-processing-commands
- docs.sixlabors.com/articles/imagesharp/security.html
- github.com/SixLabors/ImageSharp