-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:78.gssd Security Advisory The FreeBSD Project Topic: gssd maps unrecognized Kerberos principals to UID 0 Category: core Module: gssd Announced: 2026-11-17 Credits: Erik Power Credits: SecBuddyF, Tencent KeenLab Affects: FreeBSD 15.1 Corrected: 2026-11-17 17:05:52 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:08 UTC (releng/15.1, 15.1-RELEASE-p7) CVE Name: CVE-2026-101315 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background gssd(8) performs Generic Security Service Application Program Interface (GSS-API) operations on behalf of the kernel, allowing NFS to use Kerberos authentication. When a client establishes a Kerberos-authenticated session, gssd(8) on the NFS server maps the client's principal to a local user, whose credentials are used for the session. Principals with no corresponding local user are mapped to the unprivileged user "nobody". II. Problem Description When gssd(8) could not map a principal to a local user, it failed to set the user ID of the resulting credentials, leaving it as zero. The NFS server does not apply the exports(5) -maproot and -mapall options to Kerberos-authenticated requests, so the principal was granted superuser access. III. Impact A remote user holding valid Kerberos credentials for a principal that does not map to a local user on the NFS server can read and modify any file on file systems exported with Kerberos security. IV. Workaround No workaround is available. Only NFS servers running gssd(8) and exporting file systems with Kerberos security (the krb5, krb5i or krb5p flavors of the exports(5) -sec option) are affected. V. Solution Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date and restart gssd(8). Perform one of the following: 1) To update your vulnerable system installed from base system packages: Systems running a 15.0-RELEASE or later version of FreeBSD on the amd64 or arm64 platforms, which were installed using base system packages, can be updated via the pkg(8) utility: # pkg upgrade -r FreeBSD-base # service gssd restart 2) To update your vulnerable system installed from binary distribution sets: Systems running a RELEASE version of FreeBSD on the amd64 or arm64 platforms which were not installed using base system packages can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # service gssd restart 3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/SA-26:78/gssd.patch # fetch https://security.FreeBSD.org/patches/SA-26:78/gssd.patch.asc # gpg --verify gssd.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch -E -p0 < /path/to/patch c) Recompile the operating system using buildworld and installworld as described in . Restart the applicable daemons, or reboot the system. VI. Correction details This issue is corrected as of the corresponding Git commit hash in the following stable and release branches: Branch/path Hash Revision - ------------------------------------------------------------------------- stable/15/ 9bbbb1a74dc2 stable/15-n286863 releng/15.1/ 0ed72563c53b releng/15.1-n283666 - ------------------------------------------------------------------------- Run the following command to see which files were modified by a particular commit: # git show --stat Or visit the following URL, replacing NNNNNN with the hash: To determine the commit count in a working tree (for comparison against nNNNNNN in the table above), run: # git rev-list --count --first-parent HEAD VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82jkbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrvx78QAJyfpIDVM4iLGqGWz+cC MV6jHH5fLEm74hj57V55AlkuccimeJkvE4JZGgLGxWEgZf38ccnv5bwlphydZYuf c3FzEEUnV0sU3iBfoDyk790PVsF/g5MGuJWFv8iPXiptRl0Zvguectjuy6BBTejE smqgxpdaB1ALX3HiBdACbacx2cvK8UgNAlPs/lx9fVqAKgfD76ZvlxkwRGxuIEQt dRVUtAL0OsYwlxeg3jp+BhZ/4ek5XMYH9PPPXZcnR4D8lBlW9ZWqMgkEmfzHF0Na 17DQ/ju2pgnJY5R6KFmuI0XCtCoxqpz0Fh8agzwjYadb1ymjV15amu+FIN8jRDyj owDJc55/wBiCWLa+eYlsBGPTvNtVP+/0q/r3nr22qmVOG5PRlt/hG/hEPp4Cooiz Cq1RJpD8qeYOtfbN9FFXGUQsF3OJH0jCIp11HwXCYysapgjquF5fgGcMQXk1yR9H 0b4XHa7RRGUvTdiSzzAYwiCEWy4mUgiHYXfx3lgQKEIXy2iMDNQvsa60MWFPTJ1s Q3DoulHMMAliHBdNukEn3QwziRCpbKrHh91a0QcBtaBRa/8WuSvBmn7ExXzgv+Bh MCibCYZPm9Ha/lS/RlHTujdf9YdhFYtq/4CxKP2WywpSYVrGejZtWZhDzWYT/+55 8PUZl16UVebInj4czFUtJrdu =gonJ -----END PGP SIGNATURE-----