GHSA-qxrv-gp6x-rc23
MEDIUMSixLabors ImageSharp has Excessive Memory Allocation in Gif Decoder
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
SixLabors.ImageSharp.NETSixLabors.ImageSharpReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Impact
What kind of vulnerability is it? Who is impacted?
A vulnerability discovered in the ImageSharp library, where the processing of specially crafted files can lead to excessive memory usage in the Gif decoder. The vulnerability is triggered when ImageSharp attempts to process image files that are designed to exploit this flaw.
Patches
Has the problem been patched? What versions should users upgrade to?
The problem has been patched. All users are advised to upgrade to v3.1.5 or v2.1.9.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Before calling Image.Decode(Async), use Image.Identify to determine the image dimensions in order to enforce a limit.
References
Are there any links users can visit to find out more?
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | SixLabors.ImageSharp | all versions | 2.1.9 |
| .NETNuGet | SixLabors.ImageSharp | ≥ 3.0.0&&< 3.1.5 | 3.1.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for SixLabors.ImageSharp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update SixLabors.ImageSharp to 2.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qxrv-gp6x-rc23 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qxrv-gp6x-rc23 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qxrv-gp6x-rc23. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qxrv-gp6x-rc23 in your dependencies?
O3 detects GHSA-qxrv-gp6x-rc23 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.