Skip to main content
Mallory
UnratedVulnerability

CVE-2026-101312: FreeBSD VFS mount-root path traversal bypass of Capsicum and beneath-directory confinement

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-101312CWE-23

CVE-2026-101312 is a FreeBSD kernel VFS path-resolution vulnerability affecting FreeBSD 15.1 before 15.1-RELEASE-p7. It permits bypassing Capsicum and O_RESOLVE_BENEATH or AT_RESOLVE_BENEATH directory confinement when pathname resolution begins at the root of a mounted file system. During parent-directory traversal, the boundary check compares against the mount point rather than the mounted file system's root. Consequently, the check fails to recognize the starting-directory boundary and permits traversal to the mount point's parent. File-descriptor rights and normal file-system permissions remain enforced. Lookups starting in other directories are unaffected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An affected process can escape its intended starting-directory boundary and access files elsewhere beneath its process root directory. This can expose files to unauthorized reading or modification relative to the intended sandbox policy, subject to existing descriptor rights and file-system permissions. The flaw does not itself bypass those remaining access controls or establish an escape from the process root.

Mitigation

If you can’t patch tonight, do this now.

No complete workaround is available. Setting 'sysctl vfs.lookup_cap_dotdot=0' rejects all parent-directory components in capability mode and for capability-limited directory descriptors. This may break applications that rely on otherwise-safe parent-directory traversal. It does not protect O_RESOLVE_BENEATH or AT_RESOLVE_BENEATH lookups outside capability mode.

Remediation

Patch, then assume compromise.

Upgrade to FreeBSD 15.1-RELEASE-p7, FreeBSD-kernel package version 15.1_7, or a supported branch containing the correction, then reboot. Base-package installations can use 'pkg upgrade -r FreeBSD-base'; eligible binary-distribution installations can use 'freebsd-update fetch' followed by 'freebsd-update install'. Alternatively, apply the verified vendor patch, rebuild the kernel, and reboot.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-101312 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-101312 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-101312?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-101312.
Is there a patch for CVE-2026-101312?
Upgrade to FreeBSD 15.1-RELEASE-p7, FreeBSD-kernel package version 15.1_7, or a supported branch containing the correction, then reboot. Base-package installations can use 'pkg upgrade -r FreeBSD-base'; eligible binary-distribution installations can use 'freebsd-update fetch' followed by 'freebsd-update install'.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.