Skip to content
Noroxi
CVE-2024-42472· NVD / CVE Program· CNA GitHub_M

Flatpak may allow access to files outside sandbox for certain apps

Noroxi assessment

Priority: Plan (action score 40/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: 1.2% (FIRST EPSS); higher than 69.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: bubblewrap (AlmaLinux:8) 0.4.0-2.el8_10; flatpak (AlmaLinux:8) 1.12.9-3.el8_10; flatpak-devel (AlmaLinux:8) 1.12.9-3.el8_10.

Add it to your regular patch cycle. Upgrade to bubblewrap (AlmaLinux:8) 0.4.0-2.el8_10; flatpak (AlmaLinux:8) 1.12.9-3.el8_10; flatpak-devel (AlmaLinux:8) 1.12.9-3.el8_10 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

Flatpak is a Linux application sandboxing and distribution framework. Prior to versions 1.14.0 and 1.15.10, a malicious or compromised Flatpak app using persistent directories could access and write files outside of what it would otherwise have access to, which is an attack on integrity and confidentiality. When `persistent=subdir` is used in the application permissions (represented as `--persist=subdir` in the command-line interface), that means that an application which otherwise doesn't have access to the real user home directory will see an empty home directory with a writeable subdirectory `subdir`. Behind the scenes, this directory is actually a bind mount and the data is stored in the per-application directory as `~/.var/app/$APPID/subdir`. This allows existing apps that are not aware of the per-application directory to still work as intended without general home directory access. However, the application does have write access to the application directory `~/.var/app/$APPID` where this directory is stored. If the source directory for the `persistent`/`--persist` option is replaced by a symlink, then the next time the application is started, the bind mount will follow the symlink and mount whatever it points to into the sandbox. Partial protection against this vulnerability can be provided by patching Flatpak using the patches in commits ceec2ffc and 98f79773. However, this leaves a race condition that could be exploited by two instances of a malicious app running in parallel. Closing the race condition requires updating or patching the version of bubblewrap that is used by Flatpak to add the new `--bind-fd` option using the patch and then patching Flatpak to use it. If Flatpak has been configured at build-time with `-Dsystem_bubblewrap=bwrap` (1.15.x) or `--with-system-bubblewrap=bwrap` (1.14.x or older), or a similar option, then the version of bubblewrap that needs to be patched is a system copy that is distributed separately, typically `/usr/bin/bwrap`. This configuration is the one that is typically used in Linux distributions. If Flatpak has been configured at build-time with `-Dsystem_bubblewrap=` (1.15.x) or with `--without-system-bubblewrap` (1.14.x or older), then it is the bundled version of bubblewrap that is included with Flatpak that must be patched. This is typically installed as `/usr/libexec/flatpak-bwrap`. This configuration is the default when building from source code. For the 1.14.x stable branch, these changes are included in Flatpak 1.14.10. The bundled version of bubblewrap included in this release has been updated to 0.6.3. For the 1.15.x development branch, these changes are included in Flatpak 1.15.10. The bundled version of bubblewrap in this release is a Meson "wrap" subproject, which has been updated to 0.10.0. The 1.12.x and 1.10.x branches will not be updated for this vulnerability. Long-term support OS distributions should backport the individual changes into their versions of Flatpak and bubblewrap, or update to newer versions if their stability policy allows it. As a workaround, avoid using applications using the `persistent` (`--persist`) permission.

CriticalCVSS 10.0 · v3.1—No exploit Fix available
Published
Aug 15, 2024
Updated
Jun 17, 2026
EPSS
1.2% · 69th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
10.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2024-42472

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
flatpakflatpak
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • flatpak flatpak1.14.0 and later · before 1.14.10
  • flatpak flatpak1.15.0 and later · before 1.15.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • flatpak flatpak

    • < 1.14.10, >= 1.15.0, < 1.15.10affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bubblewrapbefore 0.4.0-2.el8_100.4.0-2.el8_10
AlmaLinux:8flatpakbefore 1.12.9-3.el8_101.12.9-3.el8_10
AlmaLinux:8flatpak-develbefore 1.12.9-3.el8_101.12.9-3.el8_10
AlmaLinux:8flatpak-libsbefore 1.12.9-3.el8_101.12.9-3.el8_10
AlmaLinux:8flatpak-selinuxbefore 1.12.9-3.el8_101.12.9-3.el8_10
AlmaLinux:8flatpak-session-helperbefore 1.12.9-3.el8_101.12.9-3.el8_10
AlmaLinux:9bubblewrapbefore 0.4.1-8.el9_50.4.1-8.el9_5
AlmaLinux:9bubblewrapbefore 0.4.1-7.el9_4.alma.10.4.1-7.el9_4.alma.1
AlmaLinux:9flatpakbefore 1.12.9-3.el9_51.12.9-3.el9_5
AlmaLinux:9flatpakbefore 1.12.9-3.el9_41.12.9-3.el9_4
AlmaLinux:9flatpak-develbefore 1.12.9-3.el9_51.12.9-3.el9_5
AlmaLinux:9flatpak-develbefore 1.12.9-3.el9_41.12.9-3.el9_4
AlmaLinux:9flatpak-libsbefore 1.12.9-3.el9_41.12.9-3.el9_4
AlmaLinux:9flatpak-libsbefore 1.12.9-3.el9_51.12.9-3.el9_5
AlmaLinux:9flatpak-selinuxbefore 1.12.9-3.el9_41.12.9-3.el9_4
AlmaLinux:9flatpak-selinuxbefore 1.12.9-3.el9_51.12.9-3.el9_5
AlmaLinux:9flatpak-session-helperbefore 1.12.9-3.el9_51.12.9-3.el9_5
AlmaLinux:9flatpak-session-helperbefore 1.12.9-3.el9_41.12.9-3.el9_4
Alpine:v3.20bubblewrapbefore 0.10.0-r00.10.0-r0
Debian:11flatpakbefore 1.10.8-0+deb11u31.10.8-0+deb11u3
Debian:12flatpakbefore 1.14.10-1~deb12u11.14.10-1~deb12u1
Debian:13flatpakbefore 1.14.10-11.14.10-1
openSUSE:Leap 15.5bubblewrapbefore 0.8.0-150500.3.6.10.8.0-150500.3.6.1
openSUSE:Leap 15.5flatpakbefore 1.14.5-150500.3.12.11.14.5-150500.3.12.1

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-34078Flatpak has a complete sandbox escape leading to host file access and code execution in the host context
    37Monitor
  • 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
  • CVE-2021-21261Flatpak sandbox escape via spawn portal
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-28101Mar 16, 2023 · Flatpak metadata with ANSI control codes can cause misleading terminal output
    17Monitor
  • ← EarlierCVE-2024-32462Apr 18, 2024 · Flatpak vulnerable to a sandbox escape via RequestBackground portal due to bad argument parsing
    33Monitor
  • Later →CVE-2026-34079Apr 7, 2026 · Flatpak affected by arbitrary file deletion on the host filesystem
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:bubblewrap0.4.1-7.el9_4.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:flatpak1.12.9-3.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:flatpak-devel1.12.9-3.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:flatpak-libs1.12.9-3.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:flatpak-selinux1.12.9-3.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:flatpak-session-helper1.12.9-3.el9_4 · AlmaLinux:9Package registry (OSV)
alpine:bubblewrap0.10.0-r0 · Alpine:v3.20Package registry (OSV)
debian:flatpak1.14.10-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:bubblewrap0.11.0-150500.3.9.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:flatpak1.16.0-150600.3.6.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:bubblewrap0:0.4.1-7.el9_2 · Red Hat:rhel_eus:9.2::baseosPackage registry (OSV)
red hat:bubblewrap-debuginfo0:0.4.1-7.el9_2 · Red Hat:rhel_eus:9.2::baseosPackage registry (OSV)
red hat:bubblewrap-debugsource0:0.4.1-7.el9_2 · Red Hat:rhel_eus:9.2::baseosPackage registry (OSV)
red hat:flatpak0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-debuginfo0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-debugsource0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-libs0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-libs-debuginfo0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-selinux0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-session-helper0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-session-helper-debuginfo0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:flatpak-tests-debuginfo0:1.12.7-5.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
rocky linux:bubblewrap0:0.4.0-2.el8_10 · Rocky Linux:8Package registry (OSV)
rocky linux:flatpak0:1.12.9-3.el9_5 · Rocky Linux:9Package registry (OSV)
suse:bubblewrap0.11.0-150500.3.9.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:flatpak1.16.0-150600.3.6.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP6Package registry (OSV)
suse:wayland-protocols1.36-150500.3.3.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • 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
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

nvd-secondary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records