Arbitrary file write via .ld.so symlink substitution
Published Sep 23, 2026 · Updated Sep 23, 2026
Arbitrary file write in Flatpak before 1.18.1 allows local users controlling a sandboxed app to write fixed files outside its sandbox. The regenerate_ld_cache path follows a symlink substituted for ~/.var/app/$appid/.ld.so and writes its generated cache at the symlink target. A malicious sandboxed app is required, and the fixed filenames and content substantially constrain exploitation despite allowing writes anywhere its user can access.
Summary
What happened
Arbitrary file write in Flatpak before 1.18.1 allows local users controlling a sandboxed app to write fixed files outside its sandbox. The regenerate_ld_cache path follows a symlink substituted for ~/.var/app/$appid/.ld.so and writes its generated cache at the symlink target. A malicious sandboxed app is required, and the fixed filenames and content substantially constrain exploitation despite allowing writes anywhere its user can access.
The record
- CVE
- CVE-2026-96807
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- Flatpak
- Product
- Flatpak
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.18.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started