# CVE-2024-41131: Out-of-bounds Write in SixLabors ImageSharp

> Attackers can cause a denial of service via out-of-bounds write in the GIF decoder of the ImageSharp library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** ECHO-a682-88b3-1f8b, GHSA-63p8-c4ww-9cg7

## What is CVE-2024-41131?

CVE-2024-41131 is a high-severity memory corruption vulnerability in SixLabors ImageSharp, published on 22 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ImageSharp is a 2D graphics API. An Out-of-bounds Write vulnerability has been found in the ImageSharp gif decoder, allowing attackers to cause a crash using a specially crafted gif. This can potentially lead to denial of service. All users are advised to upgrade to v3.1.5 or v2.1.9.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-41131?

4 open source packages ship an affected version, including SixLabors.ImageSharp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `SixLabors.ImageSharp` | NuGet | All versions | 2.1.9 |
| `SixLabors.ImageSharp` | NuGet | All versions | 2.1.9 |
| `SixLabors.ImageSharp` | NuGet | From 3.0.0 | 3.1.5 |
| `SixLabors.ImageSharp` | NuGet | From 3.0.0 | 3.1.5 |

Products: Sixlabors Imagesharp.

## How do I fix CVE-2024-41131?

Upgrade SixLabors.ImageSharp to a fixed version for your release line: 2.1.9 or 3.1.5.

## Is CVE-2024-41131 being exploited?

There is no known exploitation of CVE-2024-41131 in the wild and no public exploit code.

## Other vulnerabilities in SixLabors ImageSharp

- [CVE-2026-106110](https://insights.sbomify.com/CVE-2026-106110/): ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer (high 7.5)
- [CVE-2026-106112](https://insights.sbomify.com/CVE-2026-106112/): ImageSharp: ICC LUT16 output channel count can write beyond Vector4 (high 7.5)
- [CVE-2026-106113](https://insights.sbomify.com/CVE-2026-106113/): ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index (high 7.5)
- [CVE-2026-106115](https://insights.sbomify.com/CVE-2026-106115/): ImageSharp: TIFF CCITT T6 encoder writes beyond an undersized output buffer (high 7.5)
- [CVE-2026-106117](https://insights.sbomify.com/CVE-2026-106117/): ImageSharp: CCITT fax decompression (T4/Modified Huffman): unbounded WriteBits overflows strip buffer — heap OOB write in SixLabors.ImageSharp (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41131 and fix it if it is affected.

What it is: CVE-2024-41131 is a high-severity memory corruption vulnerability in SixLabors ImageSharp, published on 22 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41131 in the wild and no public exploit code.

Affected packages and fixed versions:
- SixLabors.ImageSharp (NuGet): affected all versions; fixed in 2.1.9
- SixLabors.ImageSharp (NuGet): affected all versions; fixed in 2.1.9
- SixLabors.ImageSharp (NuGet): affected from 3.0.0; fixed in 3.1.5
- SixLabors.ImageSharp (NuGet): affected from 3.0.0; fixed in 3.1.5

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-2024-41131/ (Markdown: https://insights.sbomify.com/CVE-2024-41131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41131
- OSV: https://osv.dev/vulnerability/CVE-2024-41131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41131/
Summaries are generated and may contain mistakes; the official description above is the record.