What is the CVSS score of CVE-2026-15053?

CVE-2026-15053 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.3%.

Which versions of Tanium Server are affected by CVE-2026-15053?

Tanium Server is vulnerable to a remote, unauthenticated denial-of-service attack that exhausts platform availability through memory allocation (CVE-2026-15053, CVSS 7.5).. A patch is available.

How to fix or mitigate CVE-2026-15053?

Within 24 hours: Restrict network access to Tanium Server to authorized systems only; enable real-time monitoring of server memory and CPU utilization for anomalous spikes. Within 7 days: Implement connection rate limiting and request throttling on Tanium Server interfaces; document current deployment version and identify all systems dependent on Tanium availability. Within 30 days: Monitor vendor advisory TAN-2026-016 for patch release; prepare and test patch deployment procedures.

Tanium Server CVE-2026-15053

EUVD-2026-42245 HIGH

Memory Allocation with Excessive Size Value (CWE-789)

2026-07-08 3938794e-25f5-4123-a1ba-5cbd7f104512

GHSA-83fv-4g7p-rcp3

Denial Of Service Server Tanium

7.5

CVSS 3.1 · Vendor: 3938794e-25f5-4123-a1ba-5cbd7f104512

Severity by source

Vendor (3938794e-25f5-4123-a1ba-5cbd7f104512) PRIMARY

7.5 HIGH

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

vuln.today AI

7.5 HIGH

Network-reachable management service, unauthenticated and low-complexity per vendor vector; impact is availability-only (memory exhaustion), so C:N/I:N/A:H with unchanged scope.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (3938794e-25f5-4123-a1ba-5cbd7f104512).

CVSS VectorVendor: 3938794e-25f5-4123-a1ba-5cbd7f104512

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Patch available

Jul 08, 2026 - 15:01 EUVD

Analysis Generated

Jul 08, 2026 - 14:31 vuln.today

DescriptionCVE.org

Tanium addressed a denial of service vulnerability in Tanium Server.

AnalysisAI

Denial of service in Tanium Server allows remote unauthenticated attackers to exhaust availability of the platform, per vendor advisory TAN-2026-016. The flaw is network-reachable with low complexity and no privileges or user interaction (CVSS 7.5, availability-only impact), and the CWE-789 classification indicates an uncontrolled/excessive memory allocation can be triggered remotely. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

Technical ContextAI

Tanium Server is the central management component of the Tanium endpoint management and security platform, coordinating agent (Tanium Client) communication, question distribution, and data aggregation across managed endpoints. The vulnerability is classified as CWE-789 (Memory Allocation with Excessive Size Value), meaning the server allocates memory based on an attacker-influenced size value without adequate bounds checking; a crafted request can cause the process to attempt an oversized allocation, leading to memory exhaustion or process crash. Because the Tanium Server is a network-facing service that brokers connections from clients and consoles, an allocation-based resource exhaustion bug directly threatens the availability of the entire management fabric.

RemediationAI

Apply the fixed Tanium Server release identified in vendor advisory TAN-2026-016 (https://security.tanium.com/TAN-2026-016); the exact patched version was not included in the input data and should be taken directly from that advisory. As compensating controls until patching, restrict network access to the Tanium Server management and client-facing ports so that only trusted, known endpoints and consoles can reach the service (place the server behind a firewall or restrict source IP ranges), which reduces exposure to unauthenticated remote requests at the cost of requiring accurate allow-lists for legitimate clients. Monitoring the server process for abnormal memory consumption and enabling automatic restart/watchdog behavior can reduce the duration of any successful DoS, though it does not prevent the trigger. Because this is an availability-only flaw, prioritize patching on internet-exposed or shared-network deployments first.