CVE-2026-92817

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

GHSA-q9c5-fvvm-69h6 ↗EUVD-2026-100758 ↗

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.
Inductive Automation Ignition >= 8.1.0, <= 8.1.54; >= 8.3.0, <= 8.3.8
CWE-863 Incorrect Authorization
ETK-2026-1542Zero's internal tracking ID, independent of the CVE number., permanent identifier
7d 16h 50msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+7h23m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Ignition's Perspective module can grant Designer-level access without properly enforcing session privileges. An authenticated user with access to a Vision project could gain elevated access and run code within the Ignition Gateway process.

mitigation

Upgrade Ignition 8.1 deployments to version 8.1.55 or later. Until upgraded, restrict Vision project access to trusted users and review accounts with such access.

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.
0.48%40th percentile
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 23:22Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-13 23:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1542",
  "cve_id": "CVE-2026-92817",
  "display_id": "CVE-2026-92817",
  "ghsa_id": "GHSA-q9c5-fvvm-69h6",
  "euvd_id": "EUVD-2026-100758",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization in Ignition Perspective",
  "summary": "Ignition's Perspective module can grant Designer-level access without properly enforcing session privileges. An authenticated user with access to a Vision project could gain elevated access and run code within the Ignition Gateway process.",
  "mitigation": "Upgrade Ignition 8.1 deployments to version 8.1.55 or later. Until upgraded, restrict Vision project access to trusted users and review accounts with such access.",
  "vendor": "Inductive Automation",
  "product": "Ignition",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.1.0, <= 8.1.54",
        ">= 8.3.0, <= 8.3.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Ignition",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0048,
  "epss_percentile": 0.4068,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.8123699,
  "t0_at": "2026-10-13T23:22:43.516000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T23:22:43.516000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T23:22:43.516000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92817"
    }
  }
}

published 2026-10-14 06:15Z
last change 2026-10-21 20:58Z

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.