CVE-2019-10063

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flatpak before 1.0.8, 1.1.x and 1.2.x before 1.2.4, and 1.3.x before 1.3.1 allows a sandbox bypass. Flatpak versions since 0.8.1 address CVE-2017-5226 by using a seccomp filter to prevent sandboxed apps from using the TIOCSTI ioctl, which could otherwise be used to inject commands into the controlling terminal so that they would be executed outside the sandbox after the sandboxed app exits. This fix was incomplete: on 64-bit platforms, the seccomp filter could be bypassed by an ioctl request number that has TIOCSTI in its 32 least significant bits and an arbitrary nonzero value in its 32 most significant bits, which the Linux kernel would treat as equivalent to TIOCSTI.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
46
EG Risk 46/100CISA SSVC

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
Severity90% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 26, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jul 25, 2026
Patch available. Sources: redhat.
generic

CVE-2019-10063: incomplete TIOCSTI filtering, similar to snapd's CVE-2019-7303 · Issue #2782 · flatpak/flatpak · GitHub

https://github.com/flatpak/flatpak/issues/2782
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2019:1143
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2019:1024

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatflatpak-0:1.0.6-3.el8_02019-05-13redhat
redhatflatpak-0:1.0.2-5.el7_62019-05-07redhat

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak—
  • every version up to 1.2.3-2: fixed in 1.2.3-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak—
  • every version up to 1.2.3-2: fixed in 1.2.3-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak—
  • every version up to 1.2.3-2: fixed in 1.2.3-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak—
  • every version up to 1.2.3-2: fixed in 1.2.3-2
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-09-30 14:59 UTCEPSS rescore
  5. 2026-09-30 10:07 UTCEG score recompute
  6. 2026-09-28 13:46 UTCEPSS rescore
  7. 2026-09-28 11:38 UTCOSV refresh
  8. 2026-09-27 13:40 UTCEPSS rescore
  9. 2026-09-26 15:53 UTCEPSS rescore
  10. 2026-09-26 00:20 UTCEPSS rescore
  11. 2026-09-24 13:59 UTCEPSS rescore
  12. 2026-09-23 13:43 UTCEPSS rescore
  13. 2026-09-21 20:27 UTCEPSS rescore
  14. 2026-09-20 20:10 UTCEPSS rescore
  15. 2026-09-18 19:22 UTCEPSS rescore
  16. 2026-09-17 19:22 UTCEPSS rescore
  17. 2026-09-16 14:04 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-13 16:42 UTCEPSS rescore
  20. 2026-09-12 14:56 UTCEPSS rescore
  21. 2026-09-11 14:48 UTCEPSS rescore
  22. 2026-09-08 21:55 UTCEPSS rescore
  23. 2026-09-08 15:04 UTCOSV refresh
  24. 2026-09-07 15:57 UTCEPSS rescore
  25. 2026-09-06 13:44 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:24 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:02 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 03:32 UTCEPSS rescore
  6. 2026-08-30 19:13 UTCEPSS rescore
  7. 2026-08-30 01:18 UTCEPSS rescore
  8. 2026-08-28 21:36 UTCEPSS rescore
  9. 2026-08-27 14:21 UTCEPSS rescore
  10. 2026-08-26 14:42 UTCEPSS rescore
  11. 2026-08-25 13:45 UTCEPSS rescore
  12. 2026-08-22 01:11 UTCOSV refresh
  13. 2026-08-21 23:45 UTCEPSS rescore
  14. 2026-08-20 22:51 UTCEPSS rescore
  15. 2026-08-19 17:00 UTCEPSS rescore
  16. 2026-08-18 13:44 UTCEPSS rescore
  17. 2026-08-17 13:43 UTCEPSS rescore
  18. 2026-08-16 14:52 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-13 21:56 UTCEPSS rescore
  22. 2026-08-12 13:47 UTCEPSS rescore
  23. 2026-08-09 13:43 UTCEPSS rescore
  24. 2026-08-08 16:33 UTCEPSS rescore
  25. 2026-08-07 16:23 UTCEPSS rescore
  26. 2026-08-06 13:43 UTCEPSS rescore
  27. 2026-08-06 05:54 UTCOSV refresh
  28. 2026-08-05 19:13 UTCEPSS rescore
  29. 2026-08-04 15:05 UTCEPSS rescore
  30. 2026-08-04 10:33 UTCEPSS rescore
  31. 2026-08-03 10:31 UTCEPSS rescore
  32. 2026-08-02 02:23 UTCEPSS rescore
  33. 2026-08-01 04:12 UTCEPSS rescore
  34. 2026-07-30 16:24 UTCEPSS rescore
  35. 2026-07-30 01:27 UTCEPSS rescore
  36. 2026-07-28 15:32 UTCEPSS rescore
  37. 2026-07-26 14:51 UTCEPSS rescore
  38. 2026-07-25 14:14 UTCEPSS rescore
  39. 2026-07-24 14:14 UTCEPSS rescore
  40. 2026-07-24 14:14 UTCEPSS rescore
  41. 2026-07-23 14:15 UTCEPSS rescore
  42. 2026-07-23 01:38 UTCEG score recompute
  43. 2026-07-22 22:18 UTCEG score recompute
  44. 2026-07-22 14:05 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 19:32 UTCOSV refresh
  48. 2026-07-20 17:04 UTCEPSS rescore
  49. 2026-07-19 14:28 UTCEPSS rescore
  50. 2026-07-19 14:28 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-19 02:26 UTCEPSS rescore
  53. 2026-07-18 10:01 UTCEPSS rescore
  54. 2026-07-16 16:59 UTCEPSS rescore
  55. 2026-07-16 16:59 UTCEPSS rescore
  56. 2026-07-15 16:55 UTCEPSS rescore
  57. 2026-07-13 22:27 UTCEPSS rescore
  58. 2026-07-13 06:10 UTCEPSS rescore
  59. 2026-07-13 06:10 UTCEPSS rescore
  60. 2026-07-12 05:43 UTCEPSS rescore
  61. 2026-07-11 08:24 UTCEPSS rescore
  62. 2026-07-09 19:06 UTCEPSS rescore
  63. 2026-07-08 15:11 UTCEPSS rescore
  64. 2026-07-07 13:42 UTCEPSS rescore
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 02:20 UTCEPSS rescore
  67. 2026-07-05 02:27 UTCEPSS rescore
  68. 2026-07-04 06:28 UTCEPSS rescore
  69. 2026-07-04 06:28 UTCEPSS rescore
  70. 2026-07-03 14:56 UTCOSV refresh
  71. 2026-07-02 16:56 UTCEPSS rescore
  72. 2026-07-01 15:03 UTCEPSS rescore
  73. 2026-07-01 15:03 UTCEPSS rescore
  74. 2026-06-30 23:20 UTCEPSS rescore
  75. 2026-06-30 23:20 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2019-10063?
CVE-2019-10063 is a critical vulnerability published on March 26, 2019. Flatpak before 1.0.8, 1.1.x and 1.2.x before 1.2.4, and 1.3.x before 1.3.1 allows a sandbox bypass. Flatpak versions since 0.8.1 address CVE-2017-5226 by using a seccomp filter to prevent sandboxed apps from using the TIOCSTI ioctl, which could otherwise be used to inject commands into the…
When was CVE-2019-10063 disclosed?
CVE-2019-10063 was first published on March 26, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-10063 actively exploited?
CVE-2019-10063 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-10063?
CVE-2019-10063 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2019-10063?
A fix for CVE-2019-10063 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-10063

Explore →

Is Your Infrastructure Affected by CVE-2019-10063?

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

Book a Demo →Browse All CVEs