Skip to main content
Mallory
UnratedVulnerability

CVE-2026-101315: Superuser access through unmapped Kerberos principals in FreeBSD gssd

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-101315CWE-269

FreeBSD 15.1 gssd fails to set the user ID in generated credentials when a Kerberos principal cannot be mapped to a local user, leaving the UID as zero instead of mapping the principal to the unprivileged nobody account. Consequently, a remote user with valid credentials for an unmapped principal receives superuser access to NFS file systems exported with Kerberos security. The NFS server does not apply the exports -maproot or -mapall options to Kerberos-authenticated requests, so those restrictions do not prevent exploitation.

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 authenticated remote attacker can read and modify any file within affected Kerberos-secured NFS exports with superuser privileges, compromising the confidentiality and integrity of exported data. The demonstrated scope is the exported file systems; arbitrary code execution or access to unexported file systems is not established.

Mitigation

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

No workaround is available. The NFS exports -maproot and -mapall options do not mitigate this vulnerability because they are not applied to Kerberos-authenticated requests.

Remediation

Patch, then assume compromise.

Upgrade to FreeBSD 15.1-RELEASE-p7, FreeBSD-kernel package version 15.1_7 or later, or a supported stable/security branch containing the correction, then restart gssd. For base-package installations, run 'pkg upgrade -r FreeBSD-base' followed by 'service gssd restart'. For binary distribution installations, run 'freebsd-update fetch', 'freebsd-update install', and 'service gssd restart'. Source-based installations can apply the verified security patch, rebuild and install the operating system, and restart the applicable daemons or 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-101315 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-101315 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-101315?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-101315.
Is there a patch for CVE-2026-101315?
Upgrade to FreeBSD 15.1-RELEASE-p7, FreeBSD-kernel package version 15.1_7 or later, or a supported stable/security branch containing the correction, then restart gssd. For base-package installations, run 'pkg upgrade -r FreeBSD-base' followed by 'service gssd restart'.
Activity feed

Recent activity

3 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.