util-linux is a random collection of Linux utilities. In util-linux 2.39.1 through 2.41.4 and 2.42 through 2.42.1, the SUID mount utility reads the attacker-controlled LIBMOUNT_FORCE_MOUNT2 environment variable with getenv(), allowing a local low-privileged
user to force the non-atomic legacy bind-mount path. With an /etc/fstab bind mount authorized by user or users and protected by nosuid, noexec, or nodev, an attacker can race the window between the initial bind mount and the remount that applies those security flags and execute a SUID program from the temporarily unprotected mount, potentially gaining root privileges. This issue is fixed in 2.41.5 and 2.42.2.
CVE-2026-53614
HIGHPre-NVD 7.07.0Trending — 4 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd 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: a secondary CVSS source
7.0EG
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.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.0
- EG Score
- 7.0HIGHlow confidence
- EG Risk
- 32EG Risk 32/100
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 (value × EchelonGraph’s weight)Severity70% × 45%The EG Score, 7.0 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS 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: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 2nd
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. 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.
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
October 14, 2026
Last Modified
October 15, 2026
Advisory Details (6)
Auto-updated Oct 14, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit.
GitHub commit
commit fd6b4d94ff01 (util-linux/util-linux)
Fix landed in util-linux/util-linux commit fd6b4d94ff01 — awaiting tagged release
https://github.com/util-linux/util-linux/commit/fd6b4d94ff013dc7ed680d4e864610da5b9751f1GitHub commit
commit cc81bbcec598 (util-linux/util-linux)
Fix landed in util-linux/util-linux commit cc81bbcec598 — awaiting tagged release
https://github.com/util-linux/util-linux/commit/cc81bbcec598cb91f0eb8456282f33eed820ed5fGitHub commit
commit 9cbfb823500f (util-linux/util-linux)
Fix landed in util-linux/util-linux commit 9cbfb823500f — awaiting tagged release
https://github.com/util-linux/util-linux/commit/9cbfb823500f510b34767edabd3ffd5b436987b4GitHub commit
commit 53ff0fcdab12 (util-linux/util-linux)
Fix landed in util-linux/util-linux commit 53ff0fcdab12 — awaiting tagged release
https://github.com/util-linux/util-linux/commit/53ff0fcdab12d69c60c971c69a3d0d173fa46ca9GitHub commit
commit 31e37c1c7dcf (util-linux/util-linux)
Fix landed in util-linux/util-linux commit 31e37c1c7dcf — awaiting tagged release
https://github.com/util-linux/util-linux/commit/31e37c1c7dcf25b76ccf41391fe934a75644c661GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable — nosuid/noexec Bypass in SUID mount(8) · Advisory · util-linux/util-linux · GitHub
https://github.com/util-linux/util-linux/security/advisories/GHSA-67r7-8m5w-22wxPatch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | uuid-runtime (2.37.2-4ubuntu3.6) @ jammy | 2026-10-15 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-15 16:30 UTCEG score recompute
- 2026-10-15 16:30 UTCVendor advisory
- 2026-10-15 15:23 UTCEG score recompute
- 2026-10-15 15:23 UTCVendor advisory
- 2026-10-14 17:13 UTCEG score recompute
- 2026-10-14 15:50 UTCEG score recomputeFirst assessed: 7.0 HIGH
- 2026-10-14 15:50 UTCVendor advisory
- 2026-10-14 15:49 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
4 shownubuntu:USN-8702-1
Frequently asked(5)
What is CVE-2026-53614?
CVE-2026-53614 is a high-severity vulnerability; its CVE record was published on October 14, 2026. util-linux is a random collection of Linux utilities. In util-linux 2.39.1 through 2.41.4 and 2.42 through 2.42.1, the SUID mount utility reads the attacker-controlled LIBMOUNTFORCEMOUNT2 environment variable with getenv(), allowing a local low-privileged user to force the non-atomic legacy…
When was the CVE record for CVE-2026-53614 published?
The CVE record for CVE-2026-53614 was published on October 14, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-53614 actively exploited?
CVE-2026-53614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53614?
CVE-2026-53614 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-53614?
A fix for CVE-2026-53614 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53614
Is Your Infrastructure Affected by CVE-2026-53614?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.