CVE-2026-110720

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

EUVD-2026-110070 ↗

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.
HashiCorp Tooling >= 0.42.0, < 2.0.4
fixed in 2.0.4
CWE-863 Incorrect Authorization
ETK-2026-2684Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 07msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h36m
0
+4h
+6h
+8h
+10h
+12h

description

The structured advisory metadata lists HashiCorp Tooling as affected, while the accompanying narrative identifies consul-k8s 0.42.0 and later. In the described consul-k8s issue, an attacker with existing low-level access may bypass cross-namespace ACL binding-rule authorization and obtain elevated Consul privileges.

mitigation

Upgrade Tooling to version 2.0.4. Also identify deployments using consul-k8s and upgrade them to 2.1.0 or 1.8.18 as appropriate for the supported release line.

fixed in 2.0.4

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 18:38Z
Δ 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-26 18:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2684",
  "cve_id": "CVE-2026-110720",
  "display_id": "CVE-2026-110720",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-110070",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-namespace authorization bypass in HashiCorp Tooling",
  "summary": "The structured advisory metadata lists HashiCorp Tooling as affected, while the accompanying narrative identifies consul-k8s 0.42.0 and later. In the described consul-k8s issue, an attacker with existing low-level access may bypass cross-namespace ACL binding-rule authorization and obtain elevated Consul privileges.",
  "mitigation": "Upgrade Tooling to version 2.0.4. Also identify deployments using consul-k8s and upgrade them to 2.1.0 or 1.8.18 as appropriate for the supported release line.",
  "vendor": "HashiCorp",
  "product": "Tooling",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.42.0, < 2.0.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.4"
      ],
      "package_name": "Tooling",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 37.046094933333336,
  "t0_at": "2026-10-26T18:38:14.209000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T18:38:14.209000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T18:38:14.209000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110720"
    }
  }
}

published 2026-10-26 19:36Z
last change 2026-10-26 21:01Z

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.