VulnerabilityPublished 6 Feb 2026

CVE-2025-15320: Tanium Client · Multiple Binds to the Same Port

Affects Tanium ClientSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low · fixed in 7.7.3.8231 : update Tanium Client when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

3.3Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% 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 +1

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

Attack Vector: Local
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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 6 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 Client to 7.7.3.8231, 7.6.4.2160, 7.6.2.1327 or 7.4.10.1118.

Affected software

Product	Affected	Fixed in
TaniumTanium Client	Affected >=7.7.3.0 <7.7.3.8231	Fixed in 7.7.3.8231
TaniumTanium Client	Affected >=7.6.4.0 <7.6.4.2160	Fixed in 7.6.4.2160
TaniumTanium Client	Affected >=7.6.2.0 <7.6.2.1327	Fixed in 7.6.2.1327
TaniumTanium Client	Affected >=7.4.10.0 <7.4.10.1118	Fixed in 7.4.10.1118

CPE configurations (4)

cpe:2.3:a:tanium:client:7.4.10.1116:*:*:*:*:*:*:*
cpe:2.3:a:tanium:client:7.6.2.1326:*:*:*:*:*:*:*
cpe:2.3:a:tanium:client:7.6.4.2159:*:*:*:*:*:*:*
cpe:2.3:a:tanium:client:7.7.3.8230:*:*:*:*:*:*:*

AI-suggested

2) Restrict local access to endpoints running the Tanium Client by enforcing strict access controls and using endpoint protection solutions to prevent unauthorized local logins. 3) Monitor endpoint service availability and implement alerting for Tanium Client service crashes or restarts to detect potential exploitation attempts. 4) Employ network segmentation and least privilege principles to limit the ability of attackers to gain local access. 5) Conduct regular security audits and endpoint integrity checks to identify signs of tampering or service disruption. 6) Coordinate with Tanium support for guidance on interim workarounds if patches are delayed.

Description

Tanium addressed a denial of service vulnerability in Tanium Client.

Impact

For European organizations, the primary impact of CVE-2025-15320 is on the availability of endpoint management services provided by the Tanium Client. Disruption of these services can hinder security operations, delay threat detection, and complicate incident response efforts. Organizations relying heavily on Tanium for real-time endpoint visibility and control, especially in critical infrastructure sectors such as finance, energy, and government, may experience operational challenges if the client service is rendered unavailable. Although the vulnerability does not compromise data confidentiality or integrity, the denial of service could create windows of opportunity for attackers to operate undetected. The requirement for local access limits the attack surface, but insider threats or attackers who have already gained foothold on endpoints could exploit this vulnerability to escalate disruption.

References

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

Community reviews

Loading reviews…