# CVE-2016-9969: Use after free in n/a

> A double free vulnerability in libwebpmux allows attackers to cause denial of service or potentially execute arbitrary code via crafted WebP files.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 May 2019
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-9969, GHSA-fhhw-9rjc-7m26, SUSE-SU-2025:01639-1, SUSE-SU-2025:01639-2, UBUNTU-CVE-2016-9969

## What is CVE-2016-9969?

CVE-2016-9969 is a high-severity use after free vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In libwebp 0.5.1, there is a double free bug in libwebpmux.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2016-9969?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libwebp` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 0.5.0-150000.3.17.1 |
| `libwebp` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 0.5.0-150000.3.17.1 |
| `libwebp` | SUSE:Linux Enterprise Workstation Extension 15 SP6 | All versions | 0.5.0-150000.3.17.1 |
| `libwebp` | SUSE:Linux Enterprise Workstation Extension 15 SP7 | All versions | 0.5.0-150000.3.17.1 |

Products: Webmproject Libwebp.

## How do I fix CVE-2016-9969?

Apply the vendor's patch.

## Is CVE-2016-9969 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-1999](https://insights.sbomify.com/CVE-2023-1999/): Use after free in libwebp (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9969 and fix it if it is affected.

What it is: CVE-2016-9969 is a high-severity use after free vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-9969 in the wild and no public exploit code.

Affected product: n/a. 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-2016-9969/ (Markdown: https://insights.sbomify.com/CVE-2016-9969/index.md)
```

## Sources

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

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