Tanium Discover CVE-2026-116667

Exploitation requires a valid authenticated account on Tanium Discover (PR:L - the attacker must already be logged in, not anonymous) and satisfaction of high-complexity conditions (AC:H) that the attacker cannot fully control. The specific feature, role boundary, or configuration that the improper access control violates is not described in the available sources - the advisory text was not retrieved. Limiting factors that reduce real-world risk: prior authentication is mandatory, attack complexity is high, impact is limited to partial confidentiality and integrity (no availability effect), and scope is unchanged, confining the flaw to the Discover component.

This is a moderate-severity, low-priority issue rather than an urgent threat. The CVSS 3.1 score of 4.2 reflects a network-reachable flaw (AV:N) that nonetheless requires valid low-privilege authentication (PR:L) and high attack complexity (AC:H), with only limited confidentiality and integrity impact and no availability impact (C:L/I:L/A:N, scope unchanged). The vuln.today decision label is 'this_month', signaling routine scheduled remediation rather than emergency action. No EPSS probability was supplied, so widespread-exploitation likelihood cannot be quantified from this data. The vulnerability is not listed in CISA KEV, and no proof-of-concept or exploit reference is present - only the vendor advisory. The combination of required privileges, high complexity, and bounded impact means the raw 'network vector' label overstates practical reachability: an attacker must already hold a valid account and satisfy non-trivial conditions. Note a signal conflict worth verifying with the vendor: the input Tags include 'Authentication Bypass', yet both CWE-863 (Incorrect Authorization) and the PR:L metric indicate an authorization flaw reachable by an already-authenticated user, not an authentication bypass.

An attacker who already holds valid low-privilege credentials to a Tanium Discover deployment leverages an improper access-control flaw to reach data or functionality that should be restricted to higher-privileged roles. Because the flaw carries high attack complexity (AC:H), success depends on conditions the attacker does not fully control, and impact is limited to partial disclosure or modification. No public exploit identified at time of analysis.