# CVE-2025-2849: UPX p_lx_elf.cpp un_DT_INIT heap-based overflow

> A heap-based buffer overflow in UPX allows local attackers to execute arbitrary code or cause denial of service via crafted ELF files.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2025
- **Updated:** 27 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-2849, GHSA-jrx7-5cr9-c5v4, MGASA-2025-0122, UBUNTU-CVE-2025-2849, openSUSE-SU-2025:14947-1

## What is CVE-2025-2849?

CVE-2025-2849 is a medium-severity memory corruption vulnerability in UPX, published on 27 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in UPX up to 5.0.0. Affected is the function PackLinuxElf64::un_DT_INIT of the file src/p_lx_elf.cpp. The manipulation leads to heap-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The patch is identified as e0b6ff192412f5bb5364c1948f4f6b27a0cd5ea2. It is recommended to apply a patch to fix this issue.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `upx` | openSUSE:Tumbleweed | All versions | 5.0.0-2.1 |

Products: Upx Upx.

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

Apply the vendor's patch.

## Is CVE-2025-2849 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2849 exists.

## Other vulnerabilities in UPX

- [CVE-2020-27796](https://insights.sbomify.com/CVE-2020-27796/): Memory corruption in upx (high 7.8)
- [CVE-2020-27799](https://insights.sbomify.com/CVE-2020-27799/): Memory corruption in upx (high 7.8)
- [CVE-2020-27800](https://insights.sbomify.com/CVE-2020-27800/): Memory corruption in upx (high 7.8)
- [CVE-2020-27801](https://insights.sbomify.com/CVE-2020-27801/): Memory corruption in upx (high 7.8)
- [CVE-2019-14296](https://insights.sbomify.com/CVE-2019-14296/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2849 is a medium-severity memory corruption vulnerability in UPX, published on 27 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2849 exists.

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

## Sources

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

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