CVE-2024-42472

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 1.3% (70th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-39634 (ENISA EUVD)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.3%
EPSS %ILE
70th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 15, 2024

Last Modified

August 19, 2025

Advisory Details (10)

Auto-updated Nov 8, 2026
Patch available. Sources: github, github_commit.
Web page

oss-security - flatpak CVE-2024-42472: Access to files outside sandbox for apps using persistent= (--persist)

http://www.openwall.com/lists/oss-security/2024/08/14/6
GitHub advisoryMentions a patch (unverified)

CVE-2024-42472: Access to files outside sandbox for apps using persistent= (--persist) · Advisory · flatpak/flatpak · GitHub

https://github.com/flatpak/flatpak/security/advisories/GHSA-7hgv-f2j8-xw87
GitHub commit Patch Available

commit db3a785241fd (flatpak/flatpak)

Patch available: flatpak/flatpak 1.14.10 (contains commit db3a785241fd)

https://github.com/flatpak/flatpak/commit/db3a785241fda63bf53f0ec12bb519aa5210de19
GitHub commit Patch Available

commit 8a18137d7e80 (flatpak/flatpak)

Patch available: flatpak/flatpak 1.14.10 (contains commit 8a18137d7e80)

https://github.com/flatpak/flatpak/commit/8a18137d7e80f0575e8defabf677d81e5cc3a788
GitHub commit Patch Available

commit 7c63e53bb2af (flatpak/flatpak)

Patch available: flatpak/flatpak 1.14.10 (contains commit 7c63e53bb2af)

https://github.com/flatpak/flatpak/commit/7c63e53bb2af0aae9097fd2edfd6a9ba9d453e97
GitHub commit Patch Available

commit 6bd603f6836e (flatpak/flatpak)

Patch available: flatpak/flatpak 1.15.10 (contains commit 6bd603f6836e)

https://github.com/flatpak/flatpak/commit/6bd603f6836e9b38b9b937d3b78f3fbf36e7ff75
GitHub commit Patch Available

commit 3caeb16c31a3 (flatpak/flatpak)

Patch available: flatpak/flatpak 1.15.10 (contains commit 3caeb16c31a3)

https://github.com/flatpak/flatpak/commit/3caeb16c31a3ed62d744e2aaf01d684f7991051a
GitHub commit Patch Available

commit 2cdd1e1e5ae9 (flatpak/flatpak)

Patch available: flatpak/flatpak 1.15.10 (contains commit 2cdd1e1e5ae9)

https://github.com/flatpak/flatpak/commit/2cdd1e1e5ae90d7c3a4b60ce2e36e4d609e44e72
GitHub commit Patch Available

commit a253257cd298 (containers/bubblewrap)

Patch available: containers/bubblewrap v0.10.0 (contains commit a253257cd298)

https://github.com/containers/bubblewrap/commit/a253257cd298892da43e15201d83f9a02c9b58b5
GitHub commit Patch Available

commit 68e75c3091c8 (containers/bubblewrap)

Patch available: containers/bubblewrap v0.6.3 (contains commit 68e75c3091c8)

https://github.com/containers/bubblewrap/commit/68e75c3091c87583c28a439b45c45627a94d622c

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibflatpak0 (1.6.5-0ubuntu0.5) @ focal2026-11-02ubuntu
redhatflatpak-0:1.12.9-3.el9_52024-11-12redhat
redhatflatpak-0:1.8.7-4.el8_62024-09-05redhat
redhatflatpak-0:1.10.7-4.el8_82024-09-05redhat
redhatflatpak-0:1.8.5-7.el8_42024-09-05redhat
redhatflatpak-0:1.0.9-15.el7_92024-09-05redhat
redhatflatpak-0:1.6.2-9.el8_22024-09-05redhat
redhatflatpak-0:1.12.9-3.el8_102024-09-05redhat
redhatflatpak-0:1.12.5-5.el9_02024-09-04redhat
redhatflatpak-0:1.12.7-5.el9_22024-09-04redhat
redhatflatpak-0:1.12.9-3.el9_42024-09-04redhat

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
bubblewrap—
  • every version up to 0.10.0-r0: fixed in 0.10.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
bubblewrap—
  • every version up to 0.10.0-r0: fixed in 0.10.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
bubblewrap—
  • every version up to 0.10.0-r0: fixed in 0.10.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
bubblewrap—
  • every version up to 0.10.0-r0: fixed in 0.10.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
bubblewrap—
  • every version up to 0.10.0-r0: fixed in 0.10.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak1.10.2-3 ... 1.10.8-0+deb11u2 (9 versions)
  • every version up to 1.10.8-0+deb11u3: fixed in 1.10.8-0+deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak1.14.4-1 ... 1.14.8-1~deb12u1 (9 versions)
  • every version up to 1.14.10-1~deb12u1: fixed in 1.14.10-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak—
  • every version up to 1.14.10-1: fixed in 1.14.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
flatpak—
  • every version up to 1.14.10-1: fixed in 1.14.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 19× in last 7d / 86× 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.

Showing the most recent 100 of 267 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 167 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-42472?
CVE-2024-42472 is a critical-severity vulnerability; its CVE record was published on August 15, 2024. 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…
When was the CVE record for CVE-2024-42472 published?
The CVE record for CVE-2024-42472 was published on August 15, 2024. 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 August 19, 2025; the record at its source may have been updated since.
Is CVE-2024-42472 actively exploited?
CVE-2024-42472 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-42472?
CVE-2024-42472 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-42472?
A fix for CVE-2024-42472 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-42472 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-42472

Explore →

Is Your Infrastructure Affected by CVE-2024-42472?

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