CVE-2026-87086

waiting for further signalsZero needs more public information before it can validate it.

GHSA-297h-6p2h-w2p6 ↗EUVD-2026-111257 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Tanium Provision >= 1.17, < 1.17.150; >= 1.23, < 1.23.161; >= 1.24, < 1.24.199
fixed in 1.17.150, 1.23.161, 1.24.199
CWE-690 Unchecked Return Value to NULL Pointer Dereference
ETK-2026-2793Zero's internal tracking ID, independent of the CVE number., permanent identifier
56msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h41m
0
+2h
+6h
+8h
+10h
+12h

description

Tanium Provision contains a denial-of-service vulnerability. An unauthenticated network attacker may disrupt service availability where a vulnerable Provision instance is reachable.

mitigation

Update Provision to 1.17.150, 1.23.161, or 1.24.199, as appropriate for the deployed release line. Restrict network access to Provision until the update is applied.

fixed in 1.17.150, 1.23.161, 1.24.199

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 17:35Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-27 17:35Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-87086

{
  "etk_id": "ETK-2026-2793",
  "cve_id": "CVE-2026-87086",
  "display_id": "CVE-2026-87086",
  "ghsa_id": "GHSA-297h-6p2h-w2p6",
  "euvd_id": "EUVD-2026-111257",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Denial of service in Tanium Provision",
  "summary": "Tanium Provision contains a denial-of-service vulnerability. An unauthenticated network attacker may disrupt service availability where a vulnerable Provision instance is reachable.",
  "mitigation": "Update Provision to 1.17.150, 1.23.161, or 1.24.199, as appropriate for the deployed release line. Restrict network access to Provision until the update is applied.",
  "vendor": "Tanium",
  "product": "Provision",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.17, < 1.17.150",
        ">= 1.23, < 1.23.161",
        ">= 1.24, < 1.24.199"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.17.150",
        "1.23.161",
        "1.24.199"
      ],
      "package_name": "Provision",
      "purl": null
    }
  ],
  "cwes": [
    690
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.168925466666668,
  "t0_at": "2026-10-27T17:35:23.877000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T17:35:23.877000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T17:35:23.877000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-87086"
    }
  }
}

published 2026-10-27 20:57Z
last change 2026-10-27 21:59Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.