Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-96276

Flatpak: flatpak: arbitrary write in host context via flatpak build-init

Products / packages Red Hat Enterprise Linux 10 · Red Hat Enterprise Linux 7 · Red Hat Enterprise Linux 8 · 1 more

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 21:15:32 UTC
redhat · CVSS:3.1 · 6.5
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CISA-ADP · CVSS:3.1 · 9.8
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

critical9.8

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

Flatpak has an arbitrary write vulnerability in the host context via flatpak build-init, allowing attacker-chosen files to be written outside the working directory. This occurs when a malicious SDK container declares a crafted extension point and a developer runs flatpak build-init with that SDK. The vulnerability is due to improper limitation of a pathname to a restricted directory.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Red Hat · redhat

Red Hat Enterprise Linux 10

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:enterprise_linux:10

Red Hat · redhat

Red Hat Enterprise Linux 7

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/o:redhat:rhel_els:7

Red Hat · redhat

Red Hat Enterprise Linux 8

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:enterprise_linux:8

Red Hat · redhat

Red Hat Enterprise Linux 9

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:enterprise_linux:9
Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Avoid using an non-trusted SDK for development/compilation.

redhat guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

If a malicious SDK container declares an extension point with a crafted directory 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, since the target path is resolved via a function that allows .. traversal.

References

3 sources
access.redhat.com/security/cve/CVE-2026-96276
Security advisoryredhat
bugzilla.redhat.com/show_bug.cgi
Source referenceredhat
flatpak/flatpak · security/advisories/GHSA-8qxj-x646-phcm
Security advisoryredhat

Inside the record

Evidence available

Package identity · not supplied
Version evidence · not supplied
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-96276

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-22 ↗

Improper Limitation of a Pathname to a Restricted Directory

redhat

Related →
Contributing organizations · 2
redhat

Assigning organization

2026-11-06
CISA-ADP

Additional data publisher

2026-09-23

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.