CVE-2026-39977 | flatpak -builder up to 1.4.7 g_file_resolve_relative_path path traversal

VDB-356657 · CVE-2026-39977 · GCVE-0-2026-39977 FLATPAK -BUILDER UP TO 1.4.7 G_FILE_RESOLVE_RELATIVE_PATH PATH TRAVERSAL HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.1 $0-$5k 0.74 Summaryinfo A vulnerability was found in flatpak -builder up to 1.4.7. It has been rated as critical. This issue affects the function g_file_resolve_relative_path. The manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2026-39977. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability was found in flatpak -builder up to 1.4.7 and classified as critical. This issue affects the function g_file_resolve_relative_path. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is: flatpak-builder is a tool to build flatpaks from source. From 1.4.5 to before 1.4.8, the license-files manifest key takes an array of paths to user defined licence files relative to the source directory of the module. The paths from that array are resolved using g_file_resolve_relative_path() and validated to stay inside the source directory using two checks - g_file_get_relative_path() which does not resolve symlinks and g_file_query_file_type() with G_FILE_QUERY_INFO_NOFOLLOW_SYMLINKS which only applies to the final path component. The copy operation runs on host. This can be exploited by using a crafted manifest and/or source to read arbitrary files from the host and capture them into the build output. This vulnerability is fixed in 1.4.8. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-39977 since 04/08/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue. Upgrading to version 1.4.8 eliminates this vulnerability. Productinfo Vendor flatpak Name -builder Version 1.4.0 1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6 1.4.7 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 4.3 VulDB Meta Temp Score: 4.1 VulDB Base Score: 4.3 VulDB Temp Score: 4.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Path traversal CWE: CWE-22 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: -builder 1.4.8 Timelineinfo 04/08/2026 CVE reserved 04/09/2026 +1 days Advisory disclosed 04/09/2026 +0 days VulDB entry created 04/09/2026 +0 days VulDB entry last update Sourcesinfo Advisory: github.com Status: Confirmed CVE: CVE-2026-39977 (🔒) GCVE (CVE): GCVE-0-2026-39977 GCVE (VulDB): GCVE-100-356657 Entryinfo Created: 04/09/2026 22:00 Changes: 04/09/2026 22:00 (67) Complete: 🔍 Cache ID: 99:7C5:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸