Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux. Prior to version 1.18.1, on systems where at least one OCI remote is configured (most common on Fedora systems), a malicious local user in an active local session could use a crafted architecture name to trick the flatpak-system-helper process into creating a root-owned directory tree with contents determined by the OCI remote, plus a root-owned lock file and icons directory, outside the intended root directory. If this vulnerability is combined with other vulnerabilities also fixed in 1.18.1, the combination can lead to local root privilege escalation. This particular vulnerability is not believed to be exploitable if there are no OCI remotes configured (common on non-Fedora systems). Version 1.18.1 patches the issue.
CVE-2026-92162
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (14th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-105030 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.2
- EG Score
- 7.2HIGHmedium confidence
- EG Risk
- 32EG Risk 32/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)Severity72% × 45%Impact severity (EG Severity): CVSS 7.2 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: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 14th
- 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 (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS. 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: 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).
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 20, 2026
Last Modified
October 20, 2026
Advisory Details (5)
Auto-updated Oct 20, 2026commit aeb369a27235 (flatpak/flatpak)
Patch available: flatpak/flatpak 1.18.1 (contains commit aeb369a27235)
https://github.com/flatpak/flatpak/commit/aeb369a2723506fabc1f701ef7a0dc6c97c4b983commit 19456b916842 (flatpak/flatpak)
Patch available: flatpak/flatpak 1.18.1 (contains commit 19456b916842)
https://github.com/flatpak/flatpak/commit/19456b916842b079af833a86b9ab89c5db154b92commit 01773f84021d (flatpak/flatpak)
Patch available: flatpak/flatpak 1.18.1 (contains commit 01773f84021d)
https://github.com/flatpak/flatpak/commit/01773f84021dd090b2426f79675f94f2564f9279tests: Avoid Meson's strict TAP parsing for now
Patch available: flatpak/flatpak 1.19.2 (PR #6768 merged 2026-08-11)
https://github.com/flatpak/flatpak/pull/6768CVE-2026-92162: Path traversal via unvalidated "arch" parameter in DeployAppstream · Advisory · flatpak/flatpak · GitHub
Affected: 1.18.1, the combination can lead to local root privilege escalation.
https://github.com/flatpak/flatpak/security/advisories/GHSA-v2gw-v9h5-9q4xWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 13× 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-27 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-25 13:50 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-20 16:27 UTCEG score recompute
- 2026-10-20 15:37 UTCEG score recompute
- 2026-10-20 15:26 UTCEG score recompute
- 2026-10-20 14:47 UTCEG score recomputeFirst assessed: 7.2 HIGH
- 2026-10-20 14:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-92162?
When was the CVE record for CVE-2026-92162 published?
Is CVE-2026-92162 actively exploited?
What is the CVSS score of CVE-2026-92162?
How do I remediate CVE-2026-92162?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92162
Is Your Infrastructure Affected by CVE-2026-92162?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.