CVE-2026-1344VulnerabilityPublished 17 Feb 2026

CVE-2026-1344: Tanium Enforce Recovery Key Portal · Incorrect Permissions

Affects Tanium Enforce Recovery Key PortalSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.62.5 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.62.5

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 17 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 Enforce Recovery Key Portal to 1.62.5.

Affected software

Product	Affected	Fixed in
TaniumEnforce Recovery Key Portal	Affected >=1.0.0 <1.62.5	Fixed in 1.62.5

CPE configurations (1)

cpe:2.3:a:tanium:service_enforce_recovery-key-portal:1.62.4:*:*:*:*:*:*:*

AI-suggested

1. 2. Conduct a thorough audit of file and directory permissions related to the Enforce Recovery Key Portal to ensure that only authorized users have access. 3. Restrict local access to systems running the Enforce Recovery Key Portal to trusted administrators and users with a legitimate need. 4. Implement strict access controls and monitoring on endpoints and servers hosting the portal to detect unauthorized access attempts. 5. Use endpoint detection and response (EDR) tools to monitor for suspicious local privilege escalations or file access patterns. 6. Educate internal teams about the risks of insider threats and enforce least privilege principles. 7. Regularly review and update security policies related to key management and endpoint encryption. 8. Consider network segmentation to isolate critical systems running the portal from general user environments. 9. Maintain up-to-date backups and incident response plans in case of data compromise. 10. Monitor threat intelligence feeds for any emerging exploits targeting this vulnerability.

Description

Tanium addressed an insecure file permissions vulnerability in Enforce Recovery Key Portal.

Impact

For European organizations, the exposure of recovery keys due to this vulnerability could lead to significant data confidentiality breaches, especially in sectors handling sensitive or regulated data such as finance, healthcare, and government. Attackers gaining access to recovery keys could decrypt encrypted endpoints, bypassing data protection mechanisms and potentially exfiltrating sensitive information. This could result in regulatory non-compliance with GDPR and other data protection laws, leading to legal and financial penalties. The requirement for local access and low privileges limits remote exploitation but increases risk from insider threats or attackers who have already gained limited footholds within networks. Organizations relying on Tanium for endpoint encryption key management are particularly vulnerable, and the compromise of recovery keys could undermine overall endpoint security strategies. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability details are public.

References

security.tanium.com/TAN-2026-003 (opens in a new tab)

Community reviews

Loading reviews…