# CVE-2025-15576: Jail chroot escape via fd exchange with a different jail > A jailed process can escape its chroot and access the full filesystem by exchanging directory descriptors with a sibling jail via a Unix domain socket. - **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 9 Mar 2026 - **Updated:** 10 Mar 2026 - **Also known as:** GHSA-42fj-xxgc-m676 ## What is CVE-2025-15576? CVE-2025-15576 is a high-severity vulnerability in Freebsd Freebsd, published on 9 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-790 (Improper Filtering of Special Elements), CWE-488 (Exposure of Data Element to Wrong Session), CWE-269 (Improper Privilege Management) ## Which versions are affected by CVE-2025-15576? It affects 1 product. Products: Freebsd Freebsd. ## How do I fix CVE-2025-15576? No fix has been published for CVE-2025-15576 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-15576 being exploited? There is no known exploitation of CVE-2025-15576 in the wild and no public exploit code. ## Other vulnerabilities in Freebsd Freebsd - [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0) - [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0) - [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0) - [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0) - [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-15576 and fix it if it is affected. What it is: CVE-2025-15576 is a high-severity vulnerability in Freebsd Freebsd, published on 9 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-15576 in the wild and no public exploit code. Affected product: Freebsd Freebsd. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-15576/ (Markdown: https://insights.sbomify.com/CVE-2025-15576/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15576 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15576 - OSV: https://osv.dev/vulnerability/CVE-2025-15576 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-15576/ Summaries are generated and may contain mistakes; the official description above is the record.