If two sibling jails are restricted to separate filesystem trees, which is to say that neither of the two jail root directories is an ancestor of the other, jailed processes may nonetheless be able to access a shared directory via a nullfs mount, if the administrator has configured one. In this case, cooperating processes in the two jails may establish a connection using a unix domain socket and exchange directory descriptors with each other. When performing a filesystem name lookup, at each step of the lookup, the kernel checks whether the lookup would descend below the jail root of the current process. If the jail root directory is not encountered, the lookup continues. In a configuration where processes in two different jails are able to exchange file descriptors using a unix domain socket, it is possible for a jailed process to receive a directory for a descriptor that is below that process' jail root. This enables full filesystem access for a jailed process, breaking the chroot. Note that the system administrator is still responsible for ensuring that an unprivileged user on the jail host is not able to pass directory descriptors to a jailed process, even in a patched kernel.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, requiring local system access to exploit but requires specific conditions to be met without requiring user interaction requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), for affected systems. Impacting 1 product from freebsd organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-03-09T12:16:11.523
2026-03-17T15:54:59.197
Analyzed
CVSSv3.1: 7.5 (HIGH)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For freebsd's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.