Bug 2539418 (CVE-2026-96276) - CVE-2026-96276 flatpak: flatpak: Arbitrary write in host context via flatpak build-init
Summary: CVE-2026-96276 flatpak: flatpak: Arbitrary write in host context via flatpak ...
Keywords:
Status: NEW
Alias: CVE-2026-96276
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-23 14:02 UTC by OSIDB Bzimport
Modified: 2026-09-27 19:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-23 14:02:07 UTC
GHSA-8qxj-x646-phcm (https://github.com/flatpak/flatpak/security/advisories/GHSA-8qxj-x646-phcm)

Impact: If a malicious SDK container declares an extension point with a crafted path, and a developer runs flatpak build-init --writable-sdk --sdk-extension with that SDK, attacker-chosen files could be written outside the working directory.

Description: flatpak build-init with --sdk-extensions or --base-extensions copies extension files into the build directory. The target path comes from the directory key in the extension point metadata and is resolved using g_file_resolve_relative_path, which resolves .. components. A malicious extension with directory=../../<path> causes its files to be written outside the build tree. Before copying, the target path is cleaned with flatpak_rm_rf, so existing files at the traversed path are deleted and replaced with the extension's content.

Related to GHSA-fqx6-vh4p-42cg (CVE-2026-96275); solutions share code. Fixed in 1.18.1 (backports available for 1.16.x). Reported by @swick.


Note You need to log in before you can comment on or make changes to this bug.