CVE-2026-86130

validatingZero is analyzing and reversing it now.

EUVD-2026-130522 ↗

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.
WatchGuard Dimension >= 2.0, < 2.3.2
fixed in 2.3.2
CWE-306 Missing Authentication for Critical Function
ETK-2026-4959Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 05mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+1h
+2h
+3h
+4h

description

WatchGuard Dimension releases earlier than 2.3.2 are affected in the log collection service. A remote party without credentials can submit requests that execute SQL and may lead to code execution under the WebUI process account.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade WatchGuard Dimension to version 2.3.2. Until the upgrade is complete, restrict network access to the log collection service to trusted management systems.

fixed in 2.3.2

check
building now
exploit
not yet
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.
–
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
1h 05m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 18:28Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-19 18:28Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4959",
  "cve_id": "CVE-2026-86130",
  "display_id": "CVE-2026-86130",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-130522",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Missing authentication in WatchGuard Dimension log collection",
  "summary": "WatchGuard Dimension releases earlier than 2.3.2 are affected in the log collection service. A remote party without credentials can submit requests that execute SQL and may lead to code execution under the WebUI process account.",
  "mitigation": "Upgrade WatchGuard Dimension to version 2.3.2. Until the upgrade is complete, restrict network access to the log collection service to trusted management systems.",
  "vendor": "WatchGuard",
  "product": "Dimension",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0, < 2.3.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.3.2"
      ],
      "package_name": "Dimension",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.68987185,
  "t0_at": "2026-11-19T18:28:35.031000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-19T18:28:35.031000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T18:28:35.031000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-86130"
    }
  }
}

published 2026-11-19 19:22Z
last change 2026-11-19 21:54Z

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.