CVE-2026-116662

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

GHSA-whvp-gqmc-2gpc ↗EUVD-2026-111243 ↗

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 Enforce >= 2.9, < 2.9.736; >= 2.10, < 2.10.778; >= 3.0, < 3.0.373
fixed in 2.9.736, 2.10.778, 3.0.373
ETK-2026-2794Zero's internal tracking ID, independent of the CVE number., permanent identifier
49msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h50m
0
+2h
+6h
+8h
+10h
+12h

description

Tanium Enforce is affected by a compression-bomb flaw that can consume excessive resources and disrupt availability. An unauthenticated remote attacker may be able to trigger the condition where Enforce processes attacker-supplied or attacker-influenced compressed content; the advisory does not identify the exact input path or affected versions.

mitigation

Upgrade Enforce to 2.9.736, 2.10.778, 3.0.373 or later.

fixed in 2.9.736, 2.10.778, 3.0.373

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
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 17:33Z
Δ 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:33Z
    ghsa: trigger signal, started the run
  2. 2026-10-27 17:33Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2794",
  "cve_id": "CVE-2026-116662",
  "display_id": "CVE-2026-116662",
  "ghsa_id": "GHSA-whvp-gqmc-2gpc",
  "euvd_id": "EUVD-2026-111243",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Compression bomb resource exhaustion in Tanium Enforce",
  "summary": "Tanium Enforce is affected by a compression-bomb flaw that can consume excessive resources and disrupt availability. An unauthenticated remote attacker may be able to trigger the condition where Enforce processes attacker-supplied or attacker-influenced compressed content; the advisory does not identify the exact input path or affected versions.",
  "mitigation": "Upgrade Enforce to 2.9.736, 2.10.778, 3.0.373 or later.",
  "vendor": "Tanium",
  "product": "Enforce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.9, < 2.9.736",
        ">= 2.10, < 2.10.778",
        ">= 3.0, < 3.0.373"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.9.736",
        "2.10.778",
        "3.0.373"
      ],
      "package_name": "Enforce",
      "purl": null
    }
  ],
  "cwes": null,
  "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": 22.256386383333332,
  "t0_at": "2026-10-27T17:33:33.558000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T17:33:33.558000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T17:33:33.558000+00:00",
      "url": "https://github.com/advisories/GHSA-whvp-gqmc-2gpc"
    }
  }
}

published 2026-10-27 21:00Z
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.