VulnerabilityPublished 5 Feb 2026Updated 6 Feb 2026

CVE-2025-15326: Tanium Patch · Missing Authorization

Affects Tanium PatchSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 3.19.195 or 3.17.2262 when convenient.

Data as of 26 Oct 2026, 17:16 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 3.19.195, 3.17.2262

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 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 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 Patch to 3.19.195 or 3.17.2262.

Affected software

Product	Affected	Fixed in
TaniumPatch	Affected >=3.19.0 <3.19.195	Fixed in 3.19.195
TaniumPatch	Affected >=3.17.0 <3.17.2262	Fixed in 3.17.2262

CPE configurations (2)

cpe:2.3:a:tanium:service_patch:3.17.2261:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_patch:3.19.194:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-15326, European organizations should immediately verify their Tanium Patch versions and upgrade to the latest patched releases beyond 3.19.0 where the authorization issue is resolved. Conduct a thorough audit of user privileges within Tanium Patch to ensure the principle of least privilege is enforced, limiting access only to necessary personnel. Implement network segmentation and access controls to restrict Tanium Patch management interfaces to trusted administrators and secure management networks. Enable detailed logging and monitoring of Tanium Patch access and activities to detect any unauthorized or anomalous behavior promptly. Incorporate Tanium Patch vulnerability status into broader security monitoring and incident response workflows to correlate potential reconnaissance attempts. Regularly review and update endpoint management policies to align with best practices and vendor guidance. Finally, engage with Tanium support or security advisories to stay informed about any emerging threats or additional patches related to this vulnerability.

Description

Tanium addressed an improper access controls vulnerability in Patch.

Impact

For European organizations, the primary impact of CVE-2025-15326 is the potential unauthorized disclosure of sensitive patch management data. While the vulnerability does not allow modification or disruption of services, unauthorized access to patching information could enable attackers to identify unpatched systems or security gaps, facilitating subsequent attacks. Organizations in sectors with stringent compliance requirements, such as finance, healthcare, and critical infrastructure, may face increased risk if attackers leverage this information to bypass defenses or escalate privileges. The medium severity indicates a moderate risk, but the ease of network exploitation without user interaction increases the urgency for remediation. Additionally, organizations with complex IT environments relying heavily on Tanium Patch for endpoint security management could experience operational risks if attackers gain insights into patch deployment status or configurations. Although no active exploits are known, the vulnerability could be targeted in future campaigns, especially by threat actors focusing on reconnaissance and lateral movement within networks.

References

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

Community reviews

Loading reviews…