CVE-2026-85092 jtsylve CVE debrief

Who should care

Defenders responsible for systems where LiME is used and unprivileged local users have access should assess exposure and prioritize verification of the LiME version in use. This includes operators, vulnerability management teams, and security teams who need to review and restrict write access to the output directory used by LiME and implement additional monitoring to detect potential exploitation attempts.

Why it matters

CVE-2026-85092 is a vulnerability in LiME through version 1.12.0 that allows unprivileged local users to overwrite arbitrary root-owned files.

• Verify the version of LiME in use to determine exposure.
• Assess the exposure of systems where unprivileged local users have access.
• Restrict write access to the output directory used by LiME.
• Implement additional monitoring to detect potential exploitation attempts.

Technical summary

The vulnerability allows unprivileged local users to overwrite arbitrary root-owned files by creating a symbolic link with the expected filename pointing to any root-owned file. This is caused by LiME's failure to validate the disk acquisition output path and not using O_NOFOLLOW when opening the operator-supplied path parameter. Defenders should prioritize verifying the version of LiME in use and assessing the exposure of systems where unprivileged local users have access.

Defensive priority

Defenders should prioritize verifying the version of LiME in use and assessing the exposure of systems where unprivileged local users have access.

Recommended defensive actions

• Verify the version of LiME in use and assess exposure of systems where unprivileged local users have access.
• Review and restrict write access to the output directory used by LiME.
• Implement additional monitoring to detect potential exploitation attempts.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability is caused by LiME's failure to validate the disk acquisition output path and not using O_NOFOLLOW when opening the operator-supplied path parameter. This allows unprivileged local users to overwrite arbitrary root-owned files by creating a symbolic link with the expected filename pointing to any root-owned file. Defenders should verify the version of LiME in use, assess the exposure of systems where unprivileged local users have access, and review and restrict write access to the output directory used by LiME.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.