CVE-2025-15322VulnerabilityPublished 30 Jan 2026Updated 5 Feb 2026

CVE-2025-15322: Tanium Server · Incorrect Authorization

Affects Tanium ServerSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 7.7.3.8231 : update Tanium Server when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.7.3.8231, 7.6.4.2160, 7.6.2.1327

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Tanium Server to 7.7.3.8231, 7.6.4.2160 or 7.6.2.1327.

Affected software

Product	Affected	Fixed in
TaniumTanium Server	Affected >=7.6.2.0 <7.6.2.1327 >=7.6.4.0 <7.6.4.2160 >=7.7.3.0 <7.7.3.8231	Fixed in 7.7.3.8231 7.6.4.2160 7.6.2.1327

CPE configurations (3)

cpe:2.3:a:tanium:server:7.6.2.1326:*:*:*:*:*:*:*
cpe:2.3:a:tanium:server:7.6.4.2159:*:*:*:*:*:*:*
cpe:2.3:a:tanium:server:7.7.3.8230:*:*:*:*:*:*:*

AI-suggested

Organizations should immediately inventory their Tanium Server deployments to identify affected versions (7.6.2.0, 7.6.4.0, 7.7.3.0). In the interim, review and tighten role-based access controls to ensure users have the minimum necessary privileges, and audit existing user permissions for anomalies. Implement network segmentation and restrict access to Tanium Server management interfaces to trusted administrative networks only. Enable detailed logging and monitoring of access to Tanium Server resources to detect unauthorized access attempts. Conduct regular security assessments and penetration tests focusing on authorization controls within endpoint management systems. Educate administrators about the risks of privilege misuse and enforce strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of compromised credentials being exploited. Finally, integrate this vulnerability into incident response plans to ensure rapid containment if exploitation is detected.

Description

Tanium addressed an improper access controls vulnerability in Tanium Server.

Impact

For European organizations, the primary impact is unauthorized disclosure of sensitive endpoint management data, which could include system configurations, security posture details, or operational metrics. This exposure could aid attackers in reconnaissance or lateral movement within networks. Confidentiality breaches may lead to compliance violations under GDPR if personal or sensitive data is involved. The vulnerability does not directly affect system integrity or availability, so operational disruptions are unlikely. However, the indirect risk of data leakage could undermine trust in security operations and expose organizations to targeted attacks. Organizations in sectors such as finance, healthcare, critical infrastructure, and government are particularly at risk due to the sensitive nature of the data managed by Tanium Server. The medium severity rating indicates a moderate risk level, but the ease of exploitation by users with limited privileges elevates the concern for insider threats or compromised accounts. The absence of known exploits in the wild reduces immediate risk but should not lead to complacency.

References

security.tanium.com/TAN-2025-028 (opens in a new tab)

Community reviews

Loading reviews…