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.
CVE-2026-96276
This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(low)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 23, 2026CVE-2026-96276: Arbitrary write in host context via `flatpak build-init` · Advisory · flatpak/flatpak · GitHub
Affected: version 1.18.1 by commits:
https://github.com/flatpak/flatpak/security/advisories/GHSA-8qxj-x646-phcmCVE-2026-96276 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-96276Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 15:44 UTCEG score recompute▲ 9.80
- 2026-09-23 15:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-09-23 15:17 UTCNVD update
- 2026-09-23 15:14 UTCEG score recompute
- 2026-09-23 15:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22
- CVE-2026-85706EG 10.0 KEVEPSS p95CRITICAL
- CVE-2026-82954EG 9.9CRITICAL
- CVE-2026-8859EG 9.9CRITICAL
- CVE-2026-9559EG 9.9CRITICAL
- CVE-2026-93616EG 9.8 KEVCRITICAL
- CVE-2026-89040EG 9.8CRITICAL
- CVE-2026-85661EG 9.8CRITICAL
- CVE-2026-82460EG 9.8CRITICAL
- CVE-2026-9181NVD 7.5EG 9.8CRITICAL
- CVE-2026-9129EG 9.4CRITICAL
Frequently asked(4)
What is CVE-2026-96276?
When was CVE-2026-96276 disclosed?
What is the CVSS score of CVE-2026-96276?
How do I remediate CVE-2026-96276?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96276
Is Your Infrastructure Affected by CVE-2026-96276?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.