Linux Mint Update Manager Arbitrary Code Execution Vulnerability
Is it fixed? Not yet.
Ongoing since Nov 18, 16:11 UTC. First reported Nov 18, 16:11 UTC.
What happened
A high-severity vulnerability (CVE-2026-59159) affects the Linux Mint Update Manager, allowing local users permitted to execute mint-refresh-cache through sudo to achieve arbitrary code execution as root due to lack of validation on the --parent-window-id parameter.
What caused it?
mint-refresh-cache passes a user-controlled --parent-window-id value directly to the privileged Synaptic process without validating it as an integer, allowing command-line option injection.
Source: tenable.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
Linux Mint Update Manager manages software updates Mint systems.: CVE-2026-59159 (High)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportLinux Mint Update Manager manages software updates Mint systems.: CVE-2026-59159 (High)(opens security advisory in a new tab)
High severity. Linux Mint Update Manager manages software updates on Linux Mint systems. From 5.4.8 until 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, and 6.1.5.1, mint-refresh-cache passes a user-controlled --parent-window-id value directly to the privileged Synaptic process without validating it as an integer. A local user permitted to execute mint-refresh-cache through sudo can inject additional Synaptic command-line options and achieve arbitrary code execution as root. This issue is fixed…
by Tenable 0upvotes 0comments
FAQ
What happened in the Linux issue?
A high-severity vulnerability (CVE-2026-59159) affects the Linux Mint Update Manager, allowing local users permitted to execute mint-refresh-cache through sudo to achieve arbitrary code execution as root due to lack of validation on the --parent-window-id parameter.
What is affected by the Linux issue?
Linux (versions: From 5.4.8 until 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, and 6.1.5.1).
When did the Linux issue start and end?
It started Nov 18, 16:11 UTC and is still ongoing (12 h 30 min so far). This page updates as it develops.
How do I get alerts for Linux?
Subscribe to the Linux RSS feed for every new Linux incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Linux is down. Linux feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.