CVE-2026-59159

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-129018 (ENISA EUVD)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 18, 2026

Advisory Details (7)

Auto-updated Nov 18, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit cd9799c73d0b (linuxmint/mintupdate)

Fix landed in linuxmint/mintupdate commit cd9799c73d0b — awaiting tagged release

https://github.com/linuxmint/mintupdate/commit/cd9799c73d0be7ea7539c7cddac0abc9e7f866fe
GitHub commit

commit 5a74adb19541 (linuxmint/mintupdate)

Fix landed in linuxmint/mintupdate commit 5a74adb19541 — awaiting tagged release

https://github.com/linuxmint/mintupdate/commit/5a74adb19541365317df15b9193c3d16a94012f8
GitHub commit

commit 4a5b4babf414 (linuxmint/mintupdate)

Fix landed in linuxmint/mintupdate commit 4a5b4babf414 — awaiting tagged release

https://github.com/linuxmint/mintupdate/commit/4a5b4babf4149903f833ae60217b5c62cbb2724f
GitHub commit

commit 22ad9be1a37f (linuxmint/mintupdate)

Fix landed in linuxmint/mintupdate commit 22ad9be1a37f — awaiting tagged release

https://github.com/linuxmint/mintupdate/commit/22ad9be1a37fff6363235e9c8385153460dcef9f
GitHub commit

commit 18d7a1f70c3b (linuxmint/mintupdate)

Fix landed in linuxmint/mintupdate commit 18d7a1f70c3b — awaiting tagged release

https://github.com/linuxmint/mintupdate/commit/18d7a1f70c3b57acafe9a8df0aa4f0af84b5c74c
GitHub commit

commit 0a123518753a (linuxmint/mintupdate)

Fix landed in linuxmint/mintupdate commit 0a123518753a — awaiting tagged release

https://github.com/linuxmint/mintupdate/commit/0a123518753afde7bed1b85dd8446b5c13d02509
GitHub advisoryMentions a patch (unverified)

Local privilege escalation in mint-refresh-cache via unvalidated command-line argument · Advisory · linuxmint/linuxmint · GitHub

https://github.com/linuxmint/linuxmint/security/advisories/GHSA-rq2c-p6h7-hcqq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-21 13:56 UTCOSV refresh
  3. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-20 01:36 UTCEchelonGraph re-scored
  5. 2026-11-19 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-11-18 17:29 UTCEchelonGraph re-scored
  7. 2026-11-18 17:03 UTCENISA EUVD ID recordedEUVD-2026-129018 · Source: ENISA EUVD
  8. 2026-11-18 16:38 UTCEchelonGraph re-scored
  9. 2026-11-18 16:21 UTCEchelonGraph re-scoredFirst assessed: 8.5 HIGH
  10. 2026-11-18 16:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59159?
CVE-2026-59159 is a high-severity vulnerability; its CVE record was published on November 18, 2026. 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.…
When was the CVE record for CVE-2026-59159 published?
The CVE record for CVE-2026-59159 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-59159 actively exploited?
CVE-2026-59159 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59159?
CVE-2026-59159 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59159?
The CVE record for CVE-2026-59159 names the fix: "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."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59159?

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