CVE-2026-4747 FreeBSD NFS RCE: 17-Year-Old Bug Patch Guide

CVE-2026-4747 is a memory corruption flaw in how the FreeBSD NFS client handles server responses during mount negotiation. This code path has been present in FreeBSD since approximately 2009. During the negotiation sequence, the NFS client processes server-supplied data in a way that allows an attacker-controlled server response to corrupt kernel memory, ultimately enabling arbitrary code execution in ring 0 context with root privileges.

The vulnerability requires no credentials. Any host that can reach an affected FreeBSD system over the network can trigger the flaw by sending a malformed response during the NFS mount protocol handshake. The attacker does not need an existing account on the target, knowledge of any credentials, or prior access to the system.

Seventeen-year-old bugs survive for predictable reasons. The NFS client protocol negotiation path is a rarely-audited subsystem. Code reviewers and penetration testers tend to focus on recently modified code, input validation boundaries, and high-traffic code paths. The NFS mount negotiation sequence is exercised only during mount operations, which limits how often it appears in dynamic analysis or fuzzing coverage. The triggering condition requires a specific sequence of server responses across multiple protocol states, making it resistant to surface-level fuzz testing that does not model full protocol state machines. Human auditors working under time and scope constraints made rational prioritization decisions that collectively left this code path unreviewed for over a decade.

Any FreeBSD host with NFS client functionality enabled is potentially vulnerable. The range is broader than most teams initially assume because NFS client support is compiled into the FreeBSD kernel by default and is enabled in many standard configurations.

High-risk deployment categories include FreeBSD-based NAS appliances such as FreeNAS and TrueNAS, where NFS is a primary storage protocol and often enabled by default. FreeBSD-based network appliances including pfSense and OPNsense run the affected kernel and may be vulnerable depending on configuration. FreeBSD servers in high-performance computing environments and academic data centers frequently mount shared NFS storage. FreeBSD jail-based hosting infrastructure may use NFS for shared storage between the host and jail environments.

To check whether NFS is active on a given system, run mount | grep nfs to identify currently mounted NFS shares and nfsstat -s to verify active NFS service state. Review /etc/rc.conf for nfsclient_enable entries to understand whether the NFS client starts at boot. Prioritize patching any system where NFS is confirmed active and network-accessible from untrusted hosts.

The authoritative fix is documented in the FreeBSD Security Advisory for CVE-2026-4747, published at security.freebsd.org. Apply the patch immediately using the standard FreeBSD patch mechanisms. For binary installations, freebsd-update fetch followed by freebsd-update install is the standard path. For systems built from source, apply the patches listed in the advisory and recompile the kernel.

For systems that cannot be immediately patched due to operational constraints, disable the NFS client service entirely: run service nfsclient stop to stop the running service and sysrc nfsclient_enable=NO to prevent it from starting at boot. If NFS functionality is required and cannot be disabled, apply network-level access controls at your perimeter and at the host firewall level to block NFS traffic on ports 111/TCP, 111/UDP, 2049/TCP, and 2049/UDP. Restricting NFS access to known, trusted NFS server addresses reduces exposure but does not eliminate it if any trusted server is compromised.

Verify the patch is applied by running freebsd-version -k to check the kernel version and comparing the output against the patched version string specified in the security advisory. Do not rely on uname output alone, as it may not reflect applied patches correctly in all configurations.

Claude Mythos did not find CVE-2026-4747 because it is smarter than human security researchers. It found it because it performs systematic, exhaustive analysis of code paths that humans reasonably deprioritize under time and scope constraints. Mythos traced a subtle memory management flaw through the NFS client state machine by generating and testing hypotheses for every code path, including the low-probability, rarely-exercised paths that human auditors skip.

The specific mechanism: Mythos analyzed the complete call graph of the NFS client implementation, including code paths that have not been meaningfully modified in years. It modeled the protocol state machine across multiple message exchanges and identified the specific sequence of server responses required to trigger the memory corruption. This kind of whole-codebase, whole-history analysis is computationally tractable for an AI system but practically infeasible for a human auditor working on a bounded engagement.

This is the core operational implication of Project Glasswing. The bugs that survive longest are not the ones that are hardest to understand once identified. They are the ones that exist in code paths no one thought to look at. AI-powered vulnerability research removes that assumption. Your exposure is no longer bounded by which subsystems received recent human attention. Defenders need to incorporate AI-assisted code analysis into their vulnerability management workflows, because adversaries are already testing these tools offensively. Review the free Mythos Brief at /mythos-brief for a practitioner-focused breakdown of what AI-found vulnerabilities mean for your patch and detection programs.