# CVE-2026-85092: LiME through 1.12.0 Arbitrary File Overwrite via Symlink Following

> Local attackers can overwrite root-owned files via symlink following in LiME, potentially leading to privilege escalation.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-245p-gxqq-x8q7

## What is CVE-2026-85092?

CVE-2026-85092 is a medium-severity path traversal vulnerability in jtsylve LiME, published on 3 Sep 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

LiME through 1.12.0 fails to validate the disk acquisition output path and does not use O_NOFOLLOW when opening the operator-supplied path parameter, allowing unprivileged local users to overwrite arbitrary root-owned files. An attacker who controls the output directory can create a symbolic link with the expected filename pointing to any root-owned file, and when the acquisition runs in kernel context, LiME follows the link and truncates the target file with the memory acquisition stream.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

No fix has been published for CVE-2026-85092 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85092 is a medium-severity path traversal vulnerability in jtsylve LiME, published on 3 Sep 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85092 exists.

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

## Sources

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

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