Skip to main content
Mallory
← Back to News
embedded-device-vulnerabilitywidely-deployed-product-advisoryproof-of-concept-releaseinternet-facing-service-vulnerability

FreeBSD RPCSEC_GSS Stack Overflow Enables Unauthenticated Remote Code Execution

Vulnerability Disclosure · 6 sources · Updated 5mo ago · First seen Mar 26, 2026

FreeBSD RPCSEC_GSS Stack Overflow Enables Unauthenticated Remote Code Execution

FreeBSD disclosed CVE-2026-4747 in advisory FreeBSD-SA-26:08.rpcsec_gss, warning that improper bounds checking in RPCSEC_GSS packet-signature validation can copy attacker-controlled data into a fixed stack buffer and trigger a stack overflow. The bug affects all supported FreeBSD versions and can be exploited by an unauthenticated client. In the kernel, exploitation is possible when kgssapi.ko is loaded and the system is running an NFS server with RPCSEC_GSS enabled; in userspace, RPC servers linked against librpcsec_gss are also exposed, although FreeBSD said it was not aware of vulnerable base-system applications in that category.

Independent technical write-ups tied the flaw to svc_rpc_gss_validate in the RPC/NFS path, describing how a crafted RPCSEC_GSS credential length can overflow a 128-byte stack buffer and potentially corrupt saved control data, leading to denial of service or kernel-mode remote code execution. The reports said the issue is reachable over the network, commonly via NFS on TCP port 2049, and could result in full system compromise if exploited successfully. FreeBSD released patches for supported stable and release branches and said there is no practical workaround beyond avoiding deployments where kgssapi.ko is loaded.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Mar 26, 2026 – Apr 8, 2026
  1. Apr 8, 20268mo ago

    Follow-on analysis discusses likely exploitation path and mitigations

    Additional public analysis assessed the bug as highly exploitable on FreeBSD 14.x NFS systems, citing predictable kernel addresses, limited stack protection, and ROP as a plausible route to kernel compromise. The write-ups recommended bounds checking, stronger stack-protector settings, kernel ASLR, and auditing similar RPC handling paths.

  2. Apr 8, 20268mo ago

    Third-party analyses describe stack overflow in svc_rpc_gss_validate

    Independent GitHub write-ups analyzed the flaw as a stack-based buffer overflow in FreeBSD's svc_rpc_gss_validate function, where attacker-controlled credential length can cause memcpy to overrun a fixed 128-byte stack buffer. These analyses characterized the issue as remotely reachable via crafted RPCSEC_GSS/NFS requests and potentially leading to denial of service or kernel-level remote code execution.

  3. Mar 26, 20268mo ago

    Advisory details kernel and userspace exposure conditions

    FreeBSD disclosed that kernel exploitation is possible when kgssapi.ko is loaded and an NFS server is running with RPCSEC_GSS support, allowing unauthenticated remote code execution. It also noted that RPC servers linked with librpcsec_gss are vulnerable in userspace, though it was not aware of affected base-system applications.

  4. Mar 26, 20268mo ago

    FreeBSD releases advisory and fixes for RPCSEC_GSS RCE

    The FreeBSD Project published security advisory FreeBSD-SA-26:08.rpcsec_gss for CVE-2026-4747, describing a remote code execution flaw caused by improper bounds checking in RPCSEC_GSS packet validation. FreeBSD released fixes for supported stable and release branches on the same day and said no workaround was available beyond avoiding systems with kgssapi.ko loaded.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Freebsd

Organizations

1 linked
Freebsd
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.