SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2024-32035: 0.63% estimated exploitation activity in the next 30 days; percentile 50.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A vulnerability discovered in the ImageSharp library, where the processing of specially crafted files can lead to excessive memory usage in image decoders. The vulnerability is triggered when ImageSharp attempts to process image files that are designed to exploit this flaw. This flaw can be exploited to cause a denial of service (DoS) by depleting process memory, thereby affecting applications and services that rely on ImageSharp for image processing tasks. Users and administrators are advised to update to the latest version of ImageSharp that addresses this vulnerability to mitigate the risk of exploitation. Patches The problem has been patched. All users are advised to upgrade to v3.1.4 or v2.1.8. Workarounds Before calling Image.Decode(Async), use Image.Identify to determine the image dimensions in order to enforce a limit. References - ImageSharp: Security Considerations - ImageSharp.Web: Securing Processing Commands

Published by the source

15 Apr 2024, 20:22 UTC

Last modified by the source

9 Jan 2025, 22:04 UTC

Source last checked

26 Oct 2026, 17:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g85r-6x2q-45w7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-32035

Advisory: SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value
IDs: CVE-2024-32035, GHSA-g85r-6x2q-45w7
Record: https://patchnext.com/advisories/cve-2024-32035 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sixlabors.imagesharp 3.1.4, 2.1.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet sixlabors.imagesharp: affected < 2.1.8; >= 3.0.0, < 3.1.4; fixed in 2.1.8, 3.1.4

## Suggested inspection (read-only)
- NuGet sixlabors.imagesharp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sixlabors.imagesharp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g85r-6x2q-45w7 (GitHub-reviewed advisory GHSA-g85r-6x2q-45w7 lists affected ranges: NuGet sixlabors.imagesharp >=0 =3.0.0 <3.1.4)

Commands are suggestions: review each one before running it.