LiME through 1.12.0 Arbitrary File Overwrite via Symlink Following (CVE-2026-85092) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-85092

LiME through 1.12.0 Arbitrary File Overwrite via Symlink Following

Answer in brief

CVE-2026-85092 records a Unknown severity vulnerability in LiME through 1.12.0 Arbitrary File Overwrite via Symlink Following. The current sources do not mark it as known exploited. The current feed maps jtsylve/LiME (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 3, 2026Updated Sep 3, 2026Source checked Sep 3, 2026First seen by HOL Sep 3, 2026Material review Sep 3, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps jtsylve/LiME (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
jtsylve/LiMEgeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for jtsylve/LiME.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 3, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.