Skip to main content
Mallory
HighVulnerability

CVE-2026-58092: FreeBSD mac_do Incorrect Primary Group Assignment

Published Aug 26, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS0.35%29th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-58092CWE-269

CVE-2026-58092 is an improper privilege-management vulnerability in FreeBSD 15.0 and later affecting the mac_do policy module. Following a kernel credential-layout change that moved the primary group ID into a dedicated field, the group_is_primary() function retained logic that treated the first supplementary-group entry as the primary group. When mac_do applies a matching credential-transition rule that changes identity without explicitly specifying a target group, it can assign the resulting credential the first supplementary group ID from the original credential rather than the intended primary group. If the original credential has no supplementary groups, the resulting primary group ID becomes 0, the wheel group.

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.

A process eligible for an affected mac_do transition rule can receive an unintended primary group ID. Where the process has an empty supplementary-group list, this can assign wheel-group membership. On systems whose mac_do policy or other authorization controls permit further transitions or privileged operations based on membership in group 0, the condition can provide a path to root privilege escalation. Otherwise, impact is limited to obtaining the incorrectly selected group identity.

Mitigation

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

Systems without a configured mac_do ruleset are not affected. Until patched, review, restrict, or disable mac_do transition rules that alter a UID while omitting an explicit target GID. Ensure all required transition rules explicitly set the target group, and prevent untrusted processes from obtaining the privilege required to clear supplementary groups.

Remediation

Patch, then assume compromise.

Install the FreeBSD base-system security update and reboot. Fixed revisions include stable/15-n285145, FreeBSD 15.1-RELEASE-p3, and FreeBSD 15.0-RELEASE-p13. Update through the supported FreeBSD base update mechanism, or apply the vendor patch and rebuild the kernel where applicable.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-58092 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-58092 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-58092?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-58092.
Is there a patch for CVE-2026-58092?
Install the FreeBSD base-system security update and reboot. Fixed revisions include stable/15-n285145, FreeBSD 15.1-RELEASE-p3, and FreeBSD 15.0-RELEASE-p13.
What products are affected by CVE-2026-58092?
Freebsd.
How severe is CVE-2026-58092?
CVE-2026-58092 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.35% (29th percentile) as of Sep 25, 2026.
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 activity1Community discussion across Reddit, Mastodon, and other social sources.