CVE-2026-85092

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreHIGH confidence

Score 6.6 from GitHub Security Advisory published 2026-09-03. a secondary CVSS source baseline 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.6
EG Score
6.6(high)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity66% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 10, 2026

Advisory Details (4)

Auto-updated Sep 3, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

LiME through 1.12.0 Arbitrary File Overwrite via Symlink Following | Advisories | VulnCheck

https://www.vulncheck.com/advisories/lime-through-1.12.0-arbitrary-file-overwrite-via-symlink-following
generic

GitHub - jtsylve/LiME: LiME (formerly DMD) is a Loadable Kernel Module (LKM), which allows the acquisition of volatile memory from Linux and Linux-based devices, such as those powered by Android. The tool supports acquiring memory either to the file system of the device or over the network. LiME is unique in that it is the first tool that allows full memory captures from Android devices. It also minimizes its interaction between user and kernel space processes during acquisition, which allows it...

GitHub - jtsylve/LiME: LiME (formerly DMD) is a Loadable Kernel Module (LKM), which allows the acquisition of volatile memory from Linux and Linux-based devices, such as those powered by Android. The tool supports acquiring memory either to the file system of the device or over the network. LiME is unique in that it is the first tool that allows full memory captures from Android devices. It also minimizes its interaction between user and kernel space processes during acquisition, which allows it to produce memory captures that are more forensically sound than those of other tools designed for Linux memory acquisition. · GitHub

https://github.com/jtsylve/LiME
generic

LiME/src/disk.c at v1.12.0 · jtsylve/LiME · GitHub

https://github.com/jtsylve/LiME/blob/v1.12.0/src/disk.c#L63
generic🟡 PoC Available

LiME local disk acquisition symlink following allows root-owned file overwrite · GitHub

https://gist.github.com/thesmartshadow/5355949144749b431da41490b63598f5

Vendor Advisories for CVE-2026-85092(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 09:53 UTCEG score recompute
  3. 2026-09-20 09:53 UTCGHSA enrichment
  4. 2026-09-19 07:55 UTCEG score recompute
  5. 2026-09-19 07:54 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 05:56 UTCEG score recompute
  8. 2026-09-18 05:56 UTCGHSA enrichment
  9. 2026-09-17 19:32 UTCEPSS rescore
  10. 2026-09-17 03:55 UTCEG score recompute
  11. 2026-09-17 03:55 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 01:56 UTCEG score recompute
  15. 2026-09-16 01:56 UTCGHSA enrichment
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-14 23:57 UTCGHSA enrichment
  19. 2026-09-13 21:58 UTCEG score recompute
  20. 2026-09-13 21:58 UTCGHSA enrichment
  21. 2026-09-12 19:59 UTCGHSA enrichment
  22. 2026-09-11 18:00 UTCEG score recompute
  23. 2026-09-11 18:00 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 22 more
  1. 2026-09-10 16:01 UTCEG score recompute
  2. 2026-09-10 16:01 UTCGHSA enrichment
  3. 2026-09-10 03:28 UTCGHSA enrichment
  4. 2026-09-09 01:29 UTCEG score recompute
  5. 2026-09-09 01:29 UTCGHSA enrichment
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 23:29 UTCEG score recompute
  8. 2026-09-07 23:29 UTCGHSA enrichment
  9. 2026-09-06 21:30 UTCEG score recompute
  10. 2026-09-06 21:30 UTCGHSA enrichment
  11. 2026-09-06 13:48 UTCEPSS rescore
  12. 2026-09-05 19:30 UTCEG score recompute
  13. 2026-09-05 19:30 UTCGHSA enrichment
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 17:31 UTCEG score recompute
  16. 2026-09-04 17:30 UTCGHSA enrichment
  17. 2026-09-04 05:07 UTCEPSS rescore
  18. 2026-09-03 15:31 UTCEG score recompute
  19. 2026-09-03 14:35 UTCEG score recompute
  20. 2026-09-03 13:15 UTCEG score recompute
  21. 2026-09-03 01:09 UTCEG score recompute
  22. 2026-09-03 01:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85092?
CVE-2026-85092 is a medium vulnerability published on September 3, 2026. 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…
When was CVE-2026-85092 disclosed?
CVE-2026-85092 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85092 actively exploited?
CVE-2026-85092 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-85092?
CVE-2026-85092 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-85092?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85092, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-85092

Explore →

Is Your Infrastructure Affected by CVE-2026-85092?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs