# CVE-2026-77113: Path Traversal Vulnerability in apport-unpack

> An attacker can create or overwrite arbitrary files with user privileges via crafted crash report keys in Apport.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** CLSA-2026-1792507532, GHSA-m4rr-rf2f-g267

## What is CVE-2026-77113?

CVE-2026-77113 is a medium-severity path traversal vulnerability in Canonical Apport, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Path traversal in apport-unpack in Canonical Apport before 2.36.0, 2.34.2, and 2.28.4 on Linux allows an attacker to create or overwrite arbitrary files with the privileges of the executing user via an attacker controlled key names in crash report files.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-77113?


## How do I fix CVE-2026-77113?

Upgrade to a fixed version.

## Is CVE-2026-77113 being exploited?

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

Public exploit code:

- https://github.com/0xROI/CVE-2026-77113 (github_poc): https://github.com/0xROI/CVE-2026-77113

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77113 and fix it if it is affected.

What it is: CVE-2026-77113 is a medium-severity path traversal vulnerability in Canonical Apport, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-77113 in the wild and no public exploit code.

Affected product: Canonical Apport. 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-2026-77113/ (Markdown: https://insights.sbomify.com/CVE-2026-77113/index.md)
```

## Sources

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

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