# CVE-2020-36328: Memory corruption in libwebp

> A heap-based buffer overflow in libwebp allows attackers to execute arbitrary code or cause denial of service via crafted images.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 21 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** CLSA-2025-1758615308, CLSA-2025-1758645375, DEBIAN-CVE-2020-36328, GHSA-jxwm-333p-5cwx, UBUNTU-CVE-2020-36328

## What is CVE-2020-36328?

CVE-2020-36328 is a critical memory corruption vulnerability in Apple Ipados, published on 21 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in libwebp in versions before 1.0.1. A heap-based buffer overflow in function WebPDecodeRGBInto is possible due to an invalid check for buffer size. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

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

## Which versions are affected by CVE-2020-36328?

It affects 6 products.


Products: Apple Ipados, Apple Iphone Os, Debian Debian Linux, Netapp Ontap Select Deploy Administration Utility, Redhat Enterprise Linux, Webmproject Libwebp.

## How do I fix CVE-2020-36328?

Upgrade to a fixed version.

## Is CVE-2020-36328 being exploited?

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

## Other vulnerabilities in Apple Ipados

- [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36328 and fix it if it is affected.

What it is: CVE-2020-36328 is a critical memory corruption vulnerability in Apple Ipados, published on 21 May 2021. 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-2020-36328 in the wild and no public exploit code.

Affected product: Apple Ipados. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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