Skip to main content
Menu
CVEs

CVE

Linux Mint local privilege escalation in mint-refresh-cache

Affects mintupdate 5.4.8 through 6.1.5 on systems where a local account is permitted to run mint-refresh-cache via sudo. Fixed in 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, one per release branch.

CVE-2026-59159Published Updated Summary written by a model

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, and 1 more
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Running mintupdate versions between 5.4.8 and 6.1.5 Attacker is permitted to run mint-refresh-cache via sudo

Summary

Linux Mint Update Manager's mint-refresh-cache command passes unchecked input to the privileged Synaptic process, letting a local user who is allowed to run it through sudo execute arbitrary code as root. The attacker needs only local access with a low-privilege login and no action from anyone else.

Original description

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 in versions 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.

Who should check

Teams running Linux Mint with mintupdate 5.4.8 through 6.1.5 where local users are granted sudo rights to mint-refresh-cache.

“All mintupdate versions between 5.4.8 and 6.1.5.”

github.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.5/10CVSS 8.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Running mintupdate versions between 5.4.8 and 6.1.5 Attacker is permitted to run mint-refresh-cache via sudo
  • Upgrade to a fixed version: 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, or one of 1 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-59159 (Linux Mint Update Manager: Local Privilege Escalation in mint-refresh-cache), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-59159 (entry last updated 2026-11-18):
Affected:
- linuxmint linuxmint: from 5.4.8, fixed in 5.5.4.3; from 5.5.5, fixed in 5.5.9.1; from 5.6.0, fixed in 5.8.8.1; from 5.9.0, fixed in 5.9.8.1; from 6.0.0, fixed in 6.0.9.1; from 6.1.0, fixed in 6.1.5.1
Fixed versions: 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, 6.1.5.1.
Conditions (all must be true for the bug to be hit):
- Running mintupdate versions between 5.4.8 and 6.1.5 (source: https://github.com/linuxmint/linuxmint/security/advisories/GHSA-rq2c-p6h7-hcqq)
- Attacker is permitted to run mint-refresh-cache via sudo (source: https://github.com/linuxmint/linuxmint/security/advisories/GHSA-rq2c-p6h7-hcqq)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-59159 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59159 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/linuxmint/linuxmint/security/advisories/GHSA-rq2c-p6h7-hcqq
- https://github.com/linuxmint/mintupdate/commit/0a123518753afde7bed1b85dd8446b5c13d02509
- https://github.com/linuxmint/mintupdate/commit/18d7a1f70c3b57acafe9a8df0aa4f0af84b5c74c
- https://github.com/linuxmint/mintupdate/commit/22ad9be1a37fff6363235e9c8385153460dcef9f
- https://github.com/linuxmint/mintupdate/commit/4a5b4babf4149903f833ae60217b5c62cbb2724f
- https://github.com/linuxmint/mintupdate/commit/5a74adb19541365317df15b9193c3d16a94012f8
- https://github.com/linuxmint/mintupdate/commit/cd9799c73d0be7ea7539c7cddac0abc9e7f866fe
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-59159
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-59159"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • linuxmint linuxmint

    From 5.4.8 · fixed in 5.5.4.3; From 5.5.5 · fixed in 5.5.9.1; From 5.6.0 · fixed in 5.8.8.1; From 5.9.0 · fixed in 5.9.8.1; From 6.0.0 · fixed in 6.0.9.1; From 6.1.0 · fixed in 6.1.5.1

Evidence 9

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-59159

Is CVE-2026-59159 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A local user permitted to run mint-refresh-cache via sudo can inject command-line options into it. This can lead to arbitrary code execution as root through the privileged Synaptic process.Source: github.com

Which versions are affected by CVE-2026-59159?

linuxmint: from 5.4.8 before 5.5.4.3; from 5.5.5 before 5.5.9.1; from 5.6.0 before 5.8.8.1; from 5.9.0 before 5.9.8.1; from 6.0.0 before 6.0.9.1; from 6.1.0 before 6.1.5.1.Source: cve.now feed data

Am I affected, and how do I check?

mintupdate versions from 5.4.8 through 6.1.5 are in the affected range, with each release branch fixed at a different version. The setup also requires that a local account is permitted to run mint-refresh-cache via sudo, which can be checked with sudo -l and the installed mintupdate package version with dpkg -l mintupdate.Source: github.com

How do I fix CVE-2026-59159?

Upgrade mintupdate to the fixed version for your branch: 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1 or 6.1.5.1.Source: github.com

More CVEs