# CVE-2025-48174: Integer overflow in libavif

> An integer overflow in libavif can lead to a buffer overflow, potentially allowing attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-48174, ECHO-e3e3-da97-93f7, GHSA-f6x7-5x3c-j3rg, JLSEC-2026-125, MINI-49f8-fv65-44j7, UBUNTU-CVE-2025-48174, openSUSE-SU-2025:15320-1

## What is CVE-2025-48174?

CVE-2025-48174 is a medium-severity vulnerability in aomedia libavif, published on 16 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In libavif before 1.3.0, makeRoom in stream.c has an integer overflow and resultant buffer overflow in stream->offset+size.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-48174?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libavif` | openSUSE:Tumbleweed | All versions | 1.3.0-2.1 |

Products: Aomedia Libavif.

## How do I fix CVE-2025-48174?

Upgrade to a fixed version.

## Is CVE-2025-48174 being exploited?

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

## Other vulnerabilities in aomedia libavif

- [CVE-2020-36407](https://insights.sbomify.com/CVE-2020-36407/): Memory corruption in n/a (high 8.8)
- [CVE-2025-48175](https://insights.sbomify.com/CVE-2025-48175/): Integer overflow in libavif (medium 4.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48174 and fix it if it is affected.

What it is: CVE-2025-48174 is a medium-severity vulnerability in aomedia libavif, published on 16 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48174 in the wild and no public exploit code.

Affected product: aomedia libavif. 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-2025-48174/ (Markdown: https://insights.sbomify.com/CVE-2025-48174/index.md)
```

## Sources

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

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