CVE-2026-101305: Multiple jail filesystem root escapes

Published Oct 15, 2026
·
Updated

renameat(2) did not enforce FDRESOLVEBENEATH on its directory arguments. A jailed process could rename a directory relative to a restricted descriptor, then escape the jail root via fchdir(2). This requires the directory to reside on a filesystem that is also reachable from the jail's root.

A process in a jail that has received a directory file descriptor from another jail can use these techniques to escape the jail's filesystem root restriction.

Affected Software

1 affected component
FreeBSD FreeBSD

Event History

Oct 15, 2026
CVE Published
via MITRE·06:46 AM
Data Sourced
via MITRE·06:46 AM
DescriptionWeakness

Frequently Asked Questions

1

Which jailed processes are exposed to this issue?

A jailed process is exposed when it can operate on a directory located on a filesystem that is also reachable from that jail's root. A process that has received a directory file descriptor from another jail can also use the issue to escape its filesystem-root restriction.

2

What does an attacker need to do to escape the jail filesystem root?

The attacker needs code execution in a jail and a suitable directory file descriptor or directory on a filesystem reachable from the jail root. They can use renameat(2) relative to the restricted descriptor and then use fchdir(2) to leave the jail root.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203