CVE-2025-15331VulnerabilityPublished 5 Feb 2026Updated 6 Feb 2026

CVE-2025-15331: Tanium Connect · Incomplete Cleanup

Affects Tanium ConnectSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 5.26.87 or 5.22.100 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.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.26.87, 5.22.100

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

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 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 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 Connect to 5.26.87 or 5.22.100.

Affected software

Product	Affected	Fixed in
TaniumConnect	Affected >=5.22.0 <5.22.100 >=5.26.0 <5.26.87	Fixed in 5.26.87 5.22.100

CPE configurations (2)

cpe:2.3:a:tanium:service_connect:5.22.99:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_connect:5.26.86:*:*:*:*:*:*:*

AI-suggested

2) Restrict access to Tanium Connect interfaces to trusted administrators and enforce the principle of least privilege to minimize the potential for exploitation by low-privilege users. 3) Implement network segmentation and firewall rules to limit exposure of Tanium Connect services to only necessary internal networks. 4) Monitor system resource usage closely, setting alerts for unusual spikes in CPU, memory, or other resource consumption that could indicate exploitation attempts. 5) Conduct regular audits of user accounts and permissions to detect and remove unnecessary or dormant accounts that could be leveraged by attackers. 6) Incorporate Tanium Connect into broader endpoint detection and response (EDR) monitoring to correlate any anomalies with other security events. 7) Prepare incident response plans that include scenarios involving denial of service or resource exhaustion attacks on endpoint management infrastructure. These steps go beyond generic advice by focusing on access control, monitoring, and operational readiness specific to the nature of this vulnerability.

Description

Tanium addressed an uncontrolled resource consumption vulnerability in Connect.

Impact

For European organizations, the primary impact of CVE-2025-15331 is the potential disruption of endpoint management and data integration workflows due to resource exhaustion. This could lead to degraded system performance or denial of service conditions affecting operational continuity. Organizations in sectors such as finance, healthcare, energy, and government, which often rely on Tanium Connect for real-time endpoint visibility and data aggregation, may experience interruptions that impact incident response and security monitoring capabilities. While confidentiality and integrity are not directly compromised, availability degradation can indirectly increase risk by delaying detection and response to other threats. The requirement for low privileges limits the attack surface to authenticated users or insiders, but in complex enterprise environments, lateral movement could enable exploitation. The absence of known exploits reduces immediate threat but does not eliminate the risk of future targeted attacks. European organizations with large-scale deployments of Tanium Connect should consider this vulnerability a moderate operational risk that could affect service reliability and incident handling.

References

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

Community reviews

Loading reviews…