Cyber Resilience

CVE-2026-6416

DoS in Tanium Interact 3.2.0 – 3.2.202

Published
22 April 2026
Modified
06 May 2026
Patch / advisory
CVSS Score v3.1 2.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0026 17th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-6416 is a low-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Tanium Interact. Its CVSS base score is 2.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Tanium addressed an uncontrolled resource consumption vulnerability in Interact.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Why these techniques?

CWE-400 uncontrolled resource consumption directly enables endpoint DoS via exploitation of the Tanium component.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-15289Same product: Tanium Interact
CVE-2025-15288Same product: Tanium Interact
CVE-2026-2350Same product: Tanium Interact
CVE-2026-24215Shared CWE-400
CVE-2026-20139Shared CWE-400
CVE-2026-33443Shared CWE-400
CVE-2026-8968Shared CWE-400
CVE-2024-9358Shared CWE-400
CVE-2026-42001Shared CWE-400
CVE-2026-8856Shared CWE-400

Affected Assets

tanium
interact
3.2.0 — 3.2.202 · 3.5.0 — 3.5.108 · 3.8.0 — 3.8.47

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-5 Denial-of-service Protection
  • SI-10 Information Input Validation
  • SC-6 Resource Availability
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly implements denial-of-service protections that limit or throttle resource consumption attacks matching CWE-400.

prevent

Requires validation of inputs to Tanium Interact so that malformed or excessive requests cannot trigger uncontrolled resource exhaustion.

prevent

Ensures resource availability controls (quotas, prioritization) are applied to protect against exhaustion of system resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.IR-04 mostly match
prevents

Explicitly requires monitoring and maintaining resource capacity, directly addressing uncontrolled consumption to preserve availability.

DE.CM-09 partial match
prevents

Continuous monitoring of computing resources can detect resource exhaustion but does not itself enforce allocation limits.

PR.IR-03 partial match
prevents

Resilience mechanisms such as avoiding single points of failure indirectly reduce impact of resource exhaustion.

PR.PS-01 partial match
prevents

Hardened configuration baselines can include resource quotas and limits that constrain consumption.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

prevents

By continuously monitoring utilization, stress-testing peak loads, and maintaining documented plans to scale or throttle resources, the control directly limits an attacker’s ability to drive a system into uncontrolled resource exhaustion.

detects

Pre-agreed severity-based prioritization and resource allocation during incident triage reduce the likelihood that an attacker-induced resource exhaustion will overwhelm the organization before corrective action is taken.

mitigates

Business-continuity plans that include resource-management controls reduce the likelihood that an attacker can trigger uncontrolled resource consumption by forcing the system into a degraded or fallback state.

mitigates

Defining RTOs and capacity requirements for ICT services during business-impact analysis forces organizations to provision sufficient resources and throttling mechanisms, reducing the likelihood that an attacker can induce denial-of-service through uncontrolled resource consumption.

detects

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

References