Red Hat Patches Flatpak Builder Flaw That Lets Build Sources Run Code on the Host
Red Hat published errata RHSA-2026:80973 on 12 October 2026 to fix a single security issue in flatpak-builder, the tool used to assemble flatpak application bundles from source manifests. The flaw is tracked as CVE-2026-86320 and is described as host code execution via `git am` hook execution during patch source extraction, reached through the `use-git-am` option. Red Hat Product Security has rated the update as Important and tracks the fix internally under Bugzilla 2471023. The affected platform is Red Hat Enterprise Linux 8 across x86_64, IBM z Systems (s390x), Power little endian (ppc64le) and ARM 64 (aarch64), including the Extended Life Cycle 8.10 channels for all four architectures. The corrected package is flatpak-builder-1.2.3-2.el8_10, shipped as binary, debuginfo and debugsource RPMs alongside the matching source RPM.
The advisory describes the mechanism only in outline. flatpak-builder can fetch patch sources defined in a build manifest and apply them, and when the manifest selects the `use-git-am` behaviour those patches are applied through `git am` rather than a plain patch operation. Because that path involves git's own hook handling, content supplied with the build sources can end up executing on the build host rather than being confined to the build step it was supposed to feed. Red Hat has not published a proof of concept, exploitation walkthrough or attacker telemetry in this errata, and no numeric CVSS base score appears in the advisory text itself, which instead directs readers to the CVE page for the detailed severity rating. What the advisory does state plainly is the outcome: code execution on the host that is running the build.
The practical exposure sits on developer workstations, packaging systems and CI build runners, which are precisely the hosts that handle signing material, registry credentials and artefacts that downstream users later trust. Build tooling tends to be treated as a safe context, so a manifest or patch set pulled from an external repository is often processed with far less scrutiny than an executable downloaded from the same place, and that assumption is what this flaw undermines. The blast radius is limited by the fact that someone has to build a manifest the attacker can influence, which makes the realistic scenario a supply chain one rather than a remote, unauthenticated attack. On current exploitation status, FIRST EPSS places CVE-2026-86320 at a 0.2% probability of exploitation in the next 30 days, and no in-the-wild activity is reported in the vendor errata. Organisations running RHEL 8 or its 8.10 Extended Life Cycle streams with flatpak-builder installed are the population that carries this risk, and the fixed package is already available in the Red Hat channels.
Attack Surface
Supply Chain (Third-party vendors), Endpoint OS, Server OS
Tactics
Execution, Initial Access
Techniques
- T1195.001 – Supply Chain Compromise: Compromise Software Dependencies and Development Tools
- T1059 – Command and Scripting Interpreter
- T1546 – Event Triggered Execution
SuperPRO's Threat Countermeasures Procedures
- Update flatpak-builder to 1.2.3-2.el8_10 or later on all Red Hat Enterprise Linux 8 systems (dnf update flatpak-builder), covering x86_64, s390x, ppc64le and aarch64 as well as the Extended Life Cycle 8.10 streams, per RHSA-2026:80973.
- Use the Red Hat Insights patch analysis for RHSA-2026:80973 to enumerate which registered RHEL 8 hosts still carry a vulnerable flatpak-builder build before scheduling the rollout.
- Verify the fetched packages against the published digests before installation, for example SHA-256 17dbabdd990632a37de9495c8254fb335fb9f78f48183e81230ab473d67bac32 for flatpak-builder-1.2.3-2.el8_10.src.rpm and a37c190f1ab98ec0564afd193fc3e6acbf252f6bef2064a0c3f84064b35bcbb0 for the x86_64 RPM.
- Grep build manifests and CI pipeline definitions for the use-git-am option on patch sources and disable it where it is not required, since that is the code path named in CVE-2026-86320.
- On build agents that cannot be patched immediately, neutralise repository-supplied git hooks during builds by setting a controlled hook directory, for example git config –global core.hooksPath /var/empty, so git am cannot execute hooks delivered with patch sources.
- Run flatpak-builder in a disposable container or virtual machine under a non-privileged service account with no access to signing keys or registry credentials, so host code execution during a build cannot reach production secrets.
- Add an EDR or auditd rule that alerts when a flatpak-builder or git-am process spawns a shell, interpreter or network client on packaging and CI hosts, and review any such events recorded before the patch was applied.
