Tanium addressed a server-side request forgery vulnerability in Enforce.

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Tanium/Enforce (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Tanium/Enforce.
2. 2Review the reported fix. Update Tanium/Enforce to 2.9.718 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 9, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 9, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 9, 2026

Sources and claim methodology

• Source referencesecurity.tanium.com

Related CVEs

• Tanium addressed an unauthorized code execution vulnerability in Enforce.Same tanium/enforce package
• Ninja Forms <= 3.14.6 - Authenticated (Administrator+) PHP Object Injection via Form ImportSame generic ecosystem
• H19WMIHandlerSmm: unvalidated memory boundary could result in arbitrary code execution.Same generic ecosystem
• Eventin <= 4.1.22 - Missing Authorization to Unauthenticated Arbitrary Order Creation and Status Manipulation via 'status' ParameterSame generic ecosystem
• Contact Form to DB by BestWebSoft <= 1.7.5 - Unauthenticated Stored Cross-Site Scripting via cntctfrm_contact_dropdown ParameterSame generic ecosystem
• Graphina <= 3.1.11 - Authenticated (Author+) Stored Cross-Site Scripting via 'iq_tree_tree_chart_template' Widget SettingSame generic ecosystem