Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted build manifest to victim/CI
-
DeliveryManifest references local file:// source URI
-
ExploitBuilder bypasses directory confinement check
-
ExecutionSensitive host file read into build
-
ImpactExfiltrate secrets via build artifact
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that flatpak-builder process an attacker-controlled build manifest (JSON/YAML module definition) that specifies a local file:// URI inside a source download definition; the flaw is the bypass of flatpak-builder's directory confinement checks for such local sources. Realistic preconditions and limits: the victim developer or CI system must actually run a build against the untrusted manifest (UI:R), the targeted files must be readable by the user running the build, and the practical high-value target is CI/CD pipelines that auto-build community-submitted manifests. It is not remotely exploitable without someone initiating a build, which materially constrains opportunistic exploitation. |
| Impact | This is a moderate-severity information disclosure flaw (CVSS 6.1) that is best treated as medium priority rather than an urgent fix. The provided CVSS vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) is internally consistent with the description: the attack is local in the sense that a malicious build manifest must be processed on the target host, requires no pre-existing privileges (PR:N), but hinges on user or CI interaction (UI:R) to run flatpak-builder against the attacker-supplied manifest. The high confidentiality impact (C:H) is justified because arbitrary host files readable by the build process can be exfiltrated into build artifacts. No EPSS score, KEV listing, or POC was provided; per available data there is no public exploit identified at time of analysis, so there is no evidence of active or at-scale exploitation. The key limiting factor is social-engineering/supply-chain dependency - the victim must be convinced to build an untrusted manifest - which keeps real-world risk below what the C:H impact alone might suggest. The most relevant exposure is CI/CD pipelines that automatically build third-party or community-submitted manifests, where 'user interaction' is effectively automated and secrets on the build host may be harvested. |
| Exploit ScenarioDerived | An attacker submits or publishes a crafted flatpak build manifest that references a local-file URI (e.g. file:///etc or a path to CI secrets) in a source download definition. A developer or an automated CI system processes the manifest with flatpak-builder, which fails to enforce directory confinement and reads the sensitive host file, embedding its contents into the resulting build artifact for the attacker to retrieve. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Information disclosure in flatpak-builder lets a crafted build manifest read sensitive host files and embed their contents into resulting build artifacts, because source download definitions that specify local file:// URIs bypass the tool's directory confinement checks. Exploitation requires a developer or CI system to actually process the untrusted manifest (user interaction per CVSS UI:R), so it is not remotely triggerable without someone initiating a build; no public exploit identified at time of analysis. Red Hat rates it moderate at CVSS 6.1, and the affected package ships in Red Hat Enterprise Linux 8, 9, and 10, with CI/CD pipelines that auto-build community-submitted manifests representing the highest-value target.
RemediationAI
No vendor-released patch identified at time of analysis; monitor the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-107466 and Bugzilla 2471600 for the fixed flatpak-builder package version and update through your normal RHEL errata process as soon as it is published. Until then, apply compensating controls rather than relying on defense in depth: do not run flatpak-builder against manifests from untrusted or community-submitted sources, and if CI must build such manifests, run builds inside an ephemeral, unprivileged container or sandbox whose filesystem contains no secrets (the trade-off is reduced build-time visibility and possible breakage of builds needing host tooling), and strip credentials and tokens from the build environment so there is nothing sensitive for the confinement bypass to read. A practical technical mitigation is to pre-validate or wrap builds so that any source definition containing a file:// URI is rejected before flatpak-builder runs; the side effect is that legitimate developer workflows using local path sources will need an explicit allowlist or a separate, trusted build path. Also restrict which users and CI jobs can submit manifests, since exploitation requires a victim or automation to actively process the crafted manifest.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
flatpak-builder is the command-line tool used to construct Flatpak applications from a manifest (a JSON or YAML module definition) that lists sources to be downloaded and unpacked during the build. The flaw is a path traversal class issue (CWE-22): when a source entry uses a local file:// URI rather than a remote URL, the builder fails to properly enforce the directory confinement checks that normally keep source resolution inside the expected build/download directory. Because the resolved path is not restricted to the intended root, a malicious manifest can point at arbitrary host paths readable by the user running the build. The assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) reflects a local attack requiring user interaction with no privileges needed, high confidentiality impact, low integrity impact, and no scope change. The information disclosure arises because file contents pulled in this way become part of the packaged build output, which can then be exfiltrated through the artifact itself. Affected instances are tracked via CPEs for Red Hat Enterprise Linux 8, 9, and 10, where the flatpak-builder package is distributed.
Know when Red Hat Enterprise Linux 10 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
Attack is delivered via a locally-processed manifest (AV:L) needing a build action (UI:R) but no privileges (PR:N); arbitrary host files are disclosed (C:H), artifacts are tampered (I:L), no availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in flatpak-builder. This vulnerability allows an attacker to cause information disclosure by convincing a user or continuous integration (CI) system to process a crafted build manifest. By specifying local file Uniform Resource Identifiers (URIs) within source download definitions, the builder bypasses directory confinement checks. As a result, sensitive host files accessible to the build process can be read and incorporated into the build artifacts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
More in Red Hat Enterprise Linux 10
View allHeap corruption via double-free in 389-ds-base's LDAP control parsing allows an unauthenticated remote attacker to crash
Remote code execution in Cockpit's web interface allows unauthenticated attackers to execute arbitrary commands on the h
Remote code execution in Samba's printing subsystem allows remote attackers to inject arbitrary shell commands via craft
Ghostscript can execute arbitrary shell commands with the privileges of its process when it renders a crafted PostScript
Use-after-free in librsvg during rendering of crafted SVG documents with nested XInclude directives and duplicate entity
A signed integer overflow vulnerability exists in the libtiff library's putcontig8bitYCbCr44tile function that leads to
The system CA trust store shipped in Red Hat's ca-certificates RPM packages includes eMudhra root authorities that signe
Authentication bypass in 389 Directory Server (shipped as Red Hat Directory Server 11-13 and within RHEL 6-10) lets remo
Remote code execution and privilege escalation in HPLIP (HP Linux Imaging and Printing) affects the hpcups print filter
Unauthenticated privilege escalation in FreeIPA (Red Hat Identity Management) allows a remote attacker to gain genuine a
A heap buffer overflow exists in libsoup's WebSocket permessage-deflate compression path: when a very large outbound mes
Remote code execution in libarchive on 32-bit systems allows unauthenticated attackers to execute arbitrary code via spe
EUVD-2026-94800
GHSA-m6mj-r236-h4v7
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB