CVE-2026-58092 Vulnerability Analysis & Exploit Details

CVE-2026-58092
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-58092 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-58092 Details

Status: Analyzed

Last updated: 🕜 24 Sep 2026, 13:34 UTC
Originally published on: 🕔 26 Aug 2026, 05:18 UTC

Time between publication and last update: 29 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CVE-2026-58092 Vulnerability Summary

CVE-2026-58092: In FreeBSD 15.0, the kernel structure used to represent user credentials changed: previously the primary group ID was stored in the first element of the array containing the list of supplementary group IDs, whereas now the primary group ID is stored in a dedicated field. This change was largely internal to the kernel and not user-visible. One function, group_is_primary(), was not properly updated as a part of this transition. This function is used by mac_do to determine the primary group ID of the credential after applying a transition rule, used when the rule target does not explicitly specify a group. As a result, with certain mac_do rules, it is possible for a credential switch to incorrectly set the primary group ID to the ID stored in the first element of the original credential's supplementary group array. If the list of supplementary groups is empty, this value will be 0, corresponding to the "wheel" group. For example, a rule such as "uid=1001>uid=1002" can be abused to set the primary group ID to 0 even if the process did not originally belong to group 0. Certain mac_do rules can be abused to set a process' group ID to 0. Note however, that the rule must apply to the caller in order for the bug to be triggered, e.g., given the ruleset "uid=1001>uid=1002", the user must have user ID 1001 in order to trigger the bug. Further, logged-in users will in general have a non-empty supplementary group list, in which case the bug can at worst be used to set the credential's first supplementary group ID as its primary group ID. Processes must explicitly remove themselves from all supplementary groups, using the privileged setgroups(2) system call, in order to exploit the bug to set 0 as the primary group ID. Since membership in group 0 is often used to enable controlled privilege escalation, the bug might be further exploitable to obtain root privileges, depending on the system configuration. For instance, a ruleset such as the following could be exploited by a process running as user 1001 and with an empty supplementary group list: "uid=1001>uid=1002;gid=0>uid=0".

Assessing the Risk of CVE-2026-58092

Access Complexity Graph

The exploitability of CVE-2026-58092 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-58092

CVE-2026-58092 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-58092, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-58092, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-58092 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-58092 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-58092 does not impact system availability.

CVE-2026-58092 References

External References

CWE Common Weakness Enumeration

CWE-288

CAPEC Common Attack Pattern Enumeration and Classification

  • Directory Indexing CAPEC-127 An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:o:freebsd:freebsd:15.0:p1:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p1:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p10:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p10:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p11:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p11:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p12:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p12:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p2:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p2:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p3:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p3:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p4:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p4:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p5:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p5:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p6:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p6:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p7:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p7:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p8:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p8:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.0:p9:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.0:p9:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.1:p1:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.1:p1:*:*:*:*:*:*
  • cpe:2.3:o:freebsd:freebsd:15.1:p2:*:*:*:*:*:*
    cpe:2.3:o:freebsd:freebsd:15.1:p2:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-58092: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97663 – The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up t...
  • CVE-2026-97641 – The Relevanssi – A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and i...
  • CVE-2026-97637 – The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and inclu...
  • CVE-2026-97634 – The Event Tickets and Registration plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, a...
  • CVE-2026-97342 – The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'choice' Post Meta via Inser...