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

CVE-2025-15342: Tanium Reputation · Incorrect Authorization

Affects Tanium ReputationSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 6.6.72 : update Tanium Reputation 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 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.6.72, 6.5.50, 6.3.227

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 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 Reputation to 6.6.72, 6.5.50 or 6.3.227.

Affected software

Product	Affected	Fixed in
TaniumReputation	Affected >=6.3.0 <6.3.227 >=6.5.0 <6.5.50 >=6.6.0 <6.6.72	Fixed in 6.6.72 6.5.50 6.3.227

CPE configurations (3)

cpe:2.3:a:tanium:service_reputation:6.3.226:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_reputation:6.5.49:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_reputation:6.6.71:*:*:*:*:*:*:*

AI-suggested

1. 2. In the interim, review and tighten access control policies within Tanium Reputation to minimize the number of users with low-level privileges that could exploit this flaw. 3. Implement network segmentation and restrict network access to Tanium Reputation components to trusted administrators and systems only. 4. Monitor logs and audit trails for unusual or unauthorized access attempts or configuration changes within Tanium Reputation. 5. Conduct regular security assessments and penetration tests focusing on authorization controls in security management platforms. 6. Educate administrators and security teams about the risks of improper authorization and the importance of least privilege principles. 7. Coordinate with Tanium support to confirm patch availability and receive guidance on secure configuration best practices. 8. Consider deploying additional endpoint detection and response (EDR) solutions to detect anomalous behavior that could indicate exploitation attempts.

Description

Tanium addressed an improper access controls vulnerability in Reputation.

Impact

For European organizations, the vulnerability poses a risk primarily to the integrity of security management data and configurations within Tanium Reputation. Unauthorized modification could lead to inaccurate reputation data, misclassification of threats, or manipulation of endpoint security policies, potentially weakening overall security posture. This could facilitate further attacks or evade detection. Since Tanium is widely used in large enterprises and critical infrastructure sectors, including finance, manufacturing, and government, the impact could be significant if exploited. However, the requirement for low-level privileges and no user interaction reduces the likelihood of widespread exploitation. The absence of confidentiality or availability impact limits the scope of damage but does not eliminate risks to operational trustworthiness. Organizations relying on Tanium for endpoint security telemetry and response should consider this vulnerability a moderate threat that could degrade security effectiveness if left unmitigated.

References

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

Community reviews

Loading reviews…