CVE-2018-6560: In dbus-proxy/flatpak-proxy.c in Flatpak before 0.8.9, and 0.9.x and 0.10.x before 0.10.3, crafted D-Bus messages to the host can be used to…
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: flatpak (Debian:12) 0.10.3-1; flatpak (Red Hat:enterprise_linux:7::client) 0:0.8.8-4.el7_5; flatpak-builder (Red Hat:enterprise_linux:7::client) 0:0.8.8-4.el7_5.
Low priority for now. Upgrade to flatpak (Debian:12) 0.10.3-1; flatpak (Red Hat:enterprise_linux:7::client) 0:0.8.8-4.el7_5; flatpak-builder (Red Hat:enterprise_linux:7::client) 0:0.8.8-4.el7_5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In dbus-proxy/flatpak-proxy.c in Flatpak before 0.8.9, and 0.9.x and 0.10.x before 0.10.3, crafted D-Bus messages to the host can be used to break out of the sandbox, because whitespace handling in the proxy is not identical to whitespace handling in the daemon.
- Published
- Feb 2, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-436
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| flatpak | flatpak | cpe:2.3:a:flatpak:flatpak |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux server aus | cpe:2.3:o:redhat:enterprise_linux_server_aus |
| redhat | enterprise linux server eus | cpe:2.3:o:redhat:enterprise_linux_server_eus |
| redhat | enterprise linux server tus | cpe:2.3:o:redhat:enterprise_linux_server_tus |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- flatpak flatpakbefore 0.8.9
- flatpak flatpak0.9.1 and later · up to 0.9.99 inclusive
- flatpak flatpak0.10.0 and later · before 0.10.3
- redhat enterprise linux desktop7.0
- redhat enterprise linux server7.0
- redhat enterprise linux server aus7.6
- redhat enterprise linux server eus7.5
- redhat enterprise linux server eus7.6
- redhat enterprise linux server tus7.6
- redhat enterprise linux workstation7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | flatpak | before 0.10.3-1 | 0.10.3-1 |
| Red Hat:enterprise_linux:7::client | flatpak | before 0:0.8.8-4.el7_5 | 0:0.8.8-4.el7_5 |
| Red Hat:enterprise_linux:7::client | flatpak-builder | before 0:0.8.8-4.el7_5 | 0:0.8.8-4.el7_5 |
| Red Hat:enterprise_linux:7::client | flatpak-debuginfo | before 0:0.8.8-4.el7_5 | 0:0.8.8-4.el7_5 |
| Red Hat:enterprise_linux:7::client | flatpak-devel | before 0:0.8.8-4.el7_5 | 0:0.8.8-4.el7_5 |
| Red Hat:enterprise_linux:7::client | flatpak-libs | before 0:0.8.8-4.el7_5 | 0:0.8.8-4.el7_5 |
Same product
flatpak: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-42472Flatpak may allow access to files outside sandbox for certain apps40Plan
- CVE-2026-34078Flatpak has a complete sandbox escape leading to host file access and code execution in the host context38Monitor
- CVE-2019-10063Flatpak 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.37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-9780Jun 21, 2017 · In Flatpak before 0.8.7, a third-party app repository could include malicious apps that contain files with inappropriate permissions, for…31Monitor
- Later →CVE-2019-8308Feb 12, 2019 · Flatpak before 1.0.7, and 1.1.x and 1.2.x before 1.2.3, exposes /proc in the apply_extra script sandbox, which allows attackers to modify a…32Monitor
- Later →CVE-2021-21261Jan 14, 2021 · Flatpak sandbox escape via spawn portal35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:flatpak | 0.10.3-1 · Debian:12 | Package registry (OSV) |
| red hat:flatpak | 0:0.8.8-4.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:flatpak-builder | 0:0.8.8-4.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:flatpak-debuginfo | 0:0.8.8-4.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:flatpak-devel | 0:0.8.8-4.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:flatpak-libs | 0:0.8.8-4.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-436 · Interpretation ConflictCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.