In Flatpak before 1.18.1, a malicious sandboxed app can replace ~/.var/app/$appid/.ld.so with a symlink, causing regenerate_ld_cache to write files at an arbitrary location. The filenames and content are not attacker controlled, making this hard to exploit.
CVE-2026-96807
This medium-severity CVE scores 4.0 under a secondary CVSS source (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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.0
- EG Score
- 4.0(low)
- EG Risk
- 23(Track)EG Risk 23/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 computedSeverity40% × 45%Exploitation0% × 40%Automatability30% × 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 (1)
Auto-updated Sep 23, 2026Fixed-filename writes to arbitrary locations via symlink attack on .ld.so · Advisory · flatpak/flatpak · GitHub
Affected: version 1.18.1 by commits:
https://github.com/flatpak/flatpak/security/advisories/GHSA-99wv-m8rp-g58xWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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 17:18 UTCEG score recompute
- 2026-09-23 16:59 UTCEG score recompute
- 2026-09-23 16:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-61
- CVE-2026-39861EG 10.0CRITICAL
- CVE-2026-34078EG 10.0CRITICAL
- CVE-2025-62596EG 10.0CRITICAL
- CVE-2025-62161EG 10.0CRITICAL
- CVE-2024-28189EG 10.0EPSS p94CRITICAL
- CVE-2024-28185EG 10.0EPSS p94CRITICAL
- CVE-2026-63125EG 9.9CRITICAL
- CVE-2026-91099EG 9.8CRITICAL
- CVE-2025-23394EG 9.8CRITICAL
- CVE-2024-54148EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-96807?
When was CVE-2026-96807 disclosed?
What is the CVSS score of CVE-2026-96807?
How do I remediate CVE-2026-96807?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96807
Is Your Infrastructure Affected by CVE-2026-96807?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.