How do I check whether I am affected by CVE-2026-108307?

Unknown. Check Tanium Index version in the Tanium Console against the fixed version in the Tanium advisory (security.tanium.com, published 2026-10-27) once located.

What is the fix for CVE-2026-108307?

- Apply the Tanium update that addresses this issue; the sources do not name the fixed version.

Live › vulnerability › CVE-2026-108307

Go to dashboard

high7.8Other

Tanium Index: heap buffer overflow in an unspecified component

Tanium Index has a heap-based buffer overflow that Tanium has addressed in a fix. The sources do not say what input triggers it or what an attacker gains beyond memory corruption.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

7.8

high

scored by 3938794e-25f5-4123-a1ba-5cbd7f104512

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 27, 2026 UTC
Last modified: Oct 27, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-27 18:32 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Unknown; memory corruption in Tanium Index.
CVSS said: 7.8. The facts above say medium; we keep the sources' high until an analyst looks.

Who is affected

No product ranges from the sources yet.

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-108307

Go to dashboard

high7.8Other

Tanium Index: heap buffer overflow in an unspecified component

Tanium Index has a heap-based buffer overflow that Tanium has addressed in a fix. The sources do not say what input triggers it or what an attacker gains beyond memory corruption.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

7.8

high

scored by 3938794e-25f5-4123-a1ba-5cbd7f104512

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 27, 2026 UTC
Last modified: Oct 27, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-27 18:32 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Unknown; memory corruption in Tanium Index.
CVSS said: 7.8. The facts above say medium; we keep the sources' high until an analyst looks.

Who is affected

No product ranges from the sources yet.

Know the next one before it finds you.

Add to Slack

Tanium Index: heap buffer overflow in an unspecified component

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

Tanium Index: heap buffer overflow in an unspecified component

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources