Skip to main content
Mallory
UnratedVulnerability

CVE-2026-127745: Unauthorized file truncation in FreeBSD fdescfs

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

CVE-2026-127745 is a missing-authorization vulnerability in FreeBSD's fdescfs filesystem. The filesystem omits access checks and fails to verify that a file descriptor is open for writing before permitting changes to the underlying file's size. Consequently, truncate(2) can truncate or extend a file through a read-only descriptor. Incorrect Capsicum rights checks also affect file attribute changes. All supported FreeBSD versions are affected when fdescfs is mounted without the nodup option. An unprivileged local user can alter the size of readable files, including root-owned system files, potentially causing privilege escalation or denial of service.

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 unprivileged local user can truncate or extend any file they can open for reading, bypassing the requirement for write access. Affected files can include root-owned system files. Resulting file corruption or destruction can cause denial of service and may enable privilege escalation, depending on the files affected and how privileged software uses them.

Mitigation

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

The advisory states that no workaround is available. However, systems without an fdescfs mount, or with fdescfs mounted using the nodup option, are not affected. fdescfs is not mounted by default. Administrators can inspect existing mounts with mount -t fdescfs and assess whether the affected configuration is present.

Remediation

Patch, then assume compromise.

Upgrade to a corrected FreeBSD release or stable branch and reboot. Fixed release versions are 15.1-RELEASE-p7, 14.5-RELEASE-p4, and 14.4-RELEASE-p13; corresponding FreeBSD-kernel package versions are 15.1_7, 14.5_4, and 14.4_13 or later on their respective branches. Corrections are also available in 15.2-STABLE and 14.5-STABLE as of November 17, 2026. Eligible amd64/arm64 systems using base system packages can run pkg upgrade -r FreeBSD-base. Eligible RELEASE installations using binary distribution sets can run freebsd-update fetch followed by freebsd-update install. Alternatively, verify and apply the official source 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-127745 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-127745 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-127745?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-127745.
Is there a patch for CVE-2026-127745?
Upgrade to a corrected FreeBSD release or stable branch and reboot. Fixed release versions are 15.1-RELEASE-p7, 14.5-RELEASE-p4, and 14.4-RELEASE-p13; corresponding FreeBSD-kernel package versions are 15.1_7, 14.5_4, and 14.4_13 or later on their respective branches.
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.