CVE-2026-108333: Tanium addressed a use-after-free vulnerability in Threat Response Client Extension.
Noroxi assessment
Priority: Monitor (action score 10/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Tanium threat-response-cx 1.17.802, 1.18.2732, 1.19.2213.
Low priority for now. Upgrade to Tanium threat-response-cx 1.17.802, 1.18.2732, 1.19.2213 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Oct 27, 2026
- Updated
- Nov 4, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Report tools
Action score
10
Low priority for now.
- CVSS
- 10 / 40 · 2.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Tanium
- 2.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Tanium). Independent of NVD's CPE analysis and usually ahead of it.
Tanium Endpoint Configuration Toolset Solution
- 1.51 and later · before 1.51.60affected
- 1.59 and later · before 1.59.50affected
- 1.71 and later · before 1.71.25affected
Tanium threat-response-cx
- 1.17.802 and later · before 1.17.802affected · semver
- 1.18.2732 and later · before 1.18.2732affected · semver
- 1.19.2213 and later · before 1.19.2213affected · semver
- 1.20.2271 and later · before 1.20.2271affected · semver
- 1.21.1673 and later · before 1.21.1673affected · semver
Same product
tanium: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-108307Tanium addressed a heap-based buffer overflow vulnerability in Index.31Monitor
- CVE-2026-108306Tanium addressed a local privilege escalation vulnerability in End-User Notifications.31Monitor
- CVE-2026-108305Tanium addressed a local privilege escalation vulnerability in End-User Notifications.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-108330Oct 27, 2026 · Tanium addressed an information disclosure vulnerability in Threat Response Client Extension.14Monitor
- ← EarlierCVE-2026-108331Oct 27, 2026 · Tanium addressed an infinite loop vulnerability in Threat Response Client Extension.13Monitor
- ← EarlierCVE-2026-108332Oct 27, 2026 · Tanium addressed an improper link resolution before file access vulnerability in Threat Response Client Extension.25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Tanium threat-response-cx | 1.17.802 | Vendor (CNA) |
| Tanium threat-response-cx | 1.18.2732 | Vendor (CNA) |
| Tanium threat-response-cx | 1.19.2213 | Vendor (CNA) |
| Tanium threat-response-cx | 1.20.2271 | Vendor (CNA) |
| Tanium threat-response-cx | 1.21.1673 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+17 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.