Host file writes via parent-symlink traversal
Published Sep 9, 2026 · Updated Sep 9, 2026
Path traversal in bubblewrap on Red Hat Enterprise Linux 8, 9, and 10 allows local users to write files outside a sandbox. During pre-start sandbox setup, file and directory creation under /newroot follows an attacker-controlled parent symlink through /oldroot to the host. Exploitation requires untrusted filesystem content and writes with the UID and GID of the user launching bubblewrap, without granting root privileges.
Summary
What happened
Path traversal in bubblewrap on Red Hat Enterprise Linux 8, 9, and 10 allows local users to write files outside a sandbox. During pre-start sandbox setup, file and directory creation under /newroot follows an attacker-controlled parent symlink through /oldroot to the host. Exploitation requires untrusted filesystem content and writes with the UID and GID of the user launching bubblewrap, without granting root privileges.
The record
- CVE
- CVE-2026-87766
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-59, CWE-22, T1611
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Upstream parent-symlink traversal exampleproof of concept · demonstrated
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo