NVD / CVE Program· CNA Tanium

CVE-2025-15323: Tanium addressed an improper certificate validation vulnerability in Tanium Appliance.

Noroxi assessment

Priority: Monitor (action score 14/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.16% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

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

LowCVSS 3.7 · v3.1—No exploit No fix recorded

Published: Feb 5, 2026
Updated: Jun 17, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-295

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 14 / 40 · 3.7 / 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: 3.7; 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
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

Vendor	Product	CPE
tanium	tanos	cpe:2.3:o:tanium:tanos

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

tanium tanos1.8.3 and later · before 1.8.3.0199
tanium tanos1.8.4 and later · before 1.8.4.0205
tanium tanos1.8.5 and later · before 1.8.5.0236

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 Tanium Appliance
- 1.8.3.0 and later · before 1.8.3.0199affected
- 1.8.4.0 and later · before 1.8.4.0205affected
- 1.8.5.0 and later · before 1.8.5.0236affected

Same product

tanium: all records

Other highest-scoring records for the same primary product.

CVE-2025-15311Tanium addressed an unauthorized code execution vulnerability in Tanium Appliance.
31Monitor
CVE-2025-15312Tanium addressed an improper output sanitization vulnerability in TanOS.
28Monitor
CVE-2025-13225Tanium addressed an arbitrary file deletion vulnerability in TanOS.
24Monitor

Published before and after this one in the same product

← EarlierCVE-2025-15321Feb 5, 2026 · Tanium addressed an improper input validation vulnerability in Tanium Appliance.
10Monitor
Later →CVE-2026-2605Feb 19, 2026 · Tanium addressed an insertion of sensitive information into log file vulnerability in TanOS.
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

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

nvd-secondary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
2  // Left empty for the test environment
3}

Fixed

kotlin

1val client = OkHttpClient.Builder()
2  .certificatePinner(
3    CertificatePinner.Builder()
4      .add("api.sirius.example", "sha256/…")
5      .build()
6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

security.tanium.com/TAN-2025-031

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records