VulnerabilityPublished 9 Feb 2026

CVE-2025-15317: Tanium Server · Unthrottled Resource Allocation

Affects Tanium ServerSource CVE Database V5

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

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.6.4.2124, 7.6.2.1303, 7.5.6.1164 +1

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.6.4.2124, 7.6.2.1303, 7.5.6.1164 or 7.4.6.1154.

Affected software

Product	Affected	Fixed in
TaniumTanium Server	Affected >=7.6.4.0 <7.6.4.2124	Fixed in 7.6.4.2124
TaniumTanium Server	Affected >=7.6.2.0 <7.6.2.1303	Fixed in 7.6.2.1303
TaniumTanium Server	Affected >=7.5.6.0 <7.5.6.1164	Fixed in 7.5.6.1164
TaniumTanium Server	Affected >=7.4.6.0 <7.4.6.1154	Fixed in 7.4.6.1154

CPE configurations (4)

cpe:2.3:a:tanium:server:7.4.6.1153:*:*:*:*:*:*:*
cpe:2.3:a:tanium:server:7.5.6.1163:*:*:*:*:*:*:*
cpe:2.3:a:tanium:server:7.6.2.1302:*:*:*:*:*:*:*
cpe:2.3:a:tanium:server:7.6.4.2123:*:*:*:*:*:*:*

AI-suggested

1. 2. If you cannot patch yet, implement strict network segmentation and firewall rules to limit access to Tanium Server management interfaces to trusted administrators only. 3. Monitor server resource usage closely using infrastructure monitoring tools to detect abnormal spikes indicative of exploitation attempts. 4. Configure operating system-level resource limits (e.g., cgroups on Linux or Job Objects on Windows) to cap CPU and memory usage for Tanium Server processes. 5. Employ anomaly detection systems to alert on unusual patterns of requests or resource consumption targeting Tanium Server. 6. Review and minimize the number of users with privileges sufficient to exploit this vulnerability, enforcing least privilege principles. 7. Conduct regular security audits and penetration tests focusing on endpoint management infrastructure to identify potential exploitation vectors. 8. Maintain up-to-date incident response plans that include scenarios involving denial of service on critical security infrastructure.

Description

CVE-2025-15317 is a medium severity vulnerability in Tanium Server versions 7.4.6.0, 7.5.6.0, 7.6.2.0, and 7.

Impact

For European organizations, the primary impact of CVE-2025-15317 is the potential denial of service on Tanium Server instances, which can disrupt endpoint management, security monitoring, and incident response activities. This disruption could delay detection and remediation of other security incidents, increasing overall risk exposure. Organizations in sectors relying heavily on Tanium for operational technology, critical infrastructure, or large-scale enterprise environments may experience significant operational impacts. The inability to effectively manage endpoints could lead to compliance issues with regulations such as GDPR if security controls are weakened. Additionally, service outages could affect business continuity and cause financial losses. Since the vulnerability requires only low privileges and no user interaction, insider threats or compromised low-privilege accounts could exploit it to degrade service. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

References

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

Community reviews

Loading reviews…