Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 8.8

CVE-2026-96275

Flatpak: flatpak: arbitrary write access as root via extra-data extraction

Published 23 Sept 2026 · Source updated 5 Nov 2026 · Retrieved 2026-11-05 01:18 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A malicious or compromised Flatpak repository can write attacker-controlled content to arbitrary locations on the host filesystem via extract_extra_data(). On system installs, the write happens as root. Two issues combine: `files/extra` is resolved via path operations that follow symlinks, and blob names from `xa.extra-data-sources` are not sanitized against `..` traversal.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
flatpakRed Hatunaffected: 0:1.16.0-9.el10_2.4 to < *See vendor advisory
flatpakRed Hatunaffected: 0:1.16.0-5.el10_0.6 to < *See vendor advisory
flatpakRed Hatunaffected: 0:1.12.9-7.el8_10 to < *See vendor advisory
flatpakRed Hatunaffected: 0:1.12.9-4.el9_8.4 to < *See vendor advisory
flatpakRed Hatunaffected: 0:1.12.7-5.el9_2.5 to < *See vendor advisory
flatpakRed Hatunaffected: 0:1.12.9-3.el9_4.5 to < *See vendor advisory
flatpakRed Hatunaffected: 0:1.12.9-4.el9_6.5 to < *See vendor advisory
flatpakRed HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed