CVE-2026-87766

8.8

Red Hat · Bubblewrap

A vulnerability in bubblewrap allows local attackers to escape the sandbox by following symlinks during setup, potentially writing files to the host filesystem with the privileges of the launching user.

Executive summary

A critical sandbox escape vulnerability in the bubblewrap utility, affecting various Red Hat Enterprise Linux versions, allows local attackers to gain unauthorized access to the host filesystem.

Vulnerability

This flaw involves improper link resolution (CWE-59) during the sandbox initialization process, where the application fails to safely handle parent symlinks. An attacker with local access and low privileges can exploit this to write files outside the intended sandbox boundary.

Business impact

The ability to write arbitrary files to the host system from within a sandbox environment constitutes a significant security compromise. This breach of isolation can lead to full host system compromise, privilege escalation, and unauthorized data access, justifying the CVSS 8.8 High severity rating.

Remediation

Immediate Action: Update the bubblewrap package to version 0.12.0 or later as provided by your Red Hat distribution channels.

Proactive Monitoring: Review system audit logs for unusual file write operations or unexpected processes executing with elevated permissions originating from sandboxed environments.

Compensating Controls: Restrict the ability of untrusted users to initiate sandboxed processes if an immediate update is not feasible.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the severity of this sandbox escape, organizations should prioritize patching all affected Red Hat Enterprise Linux systems. Failure to address this vulnerability allows local users to circumvent security boundaries, creating a direct path to host system compromise. Promptly applying the vendor provided update is the only effective way to neutralize this risk.

More Red Hat CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Red Hat would like to thank geeknik for reporting this issue., per the CVE Program record.