CVE-2026-92450

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

EUVD-2026-108550 ↗

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.
Kiloview E3 Firmware < 1.30
fixed in 1.30
CWE-798 Use of Hard-coded Credentials
ETK-2026-2514Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 29msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h50m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Kiloview E3 NDI encoder firmware uses the same embedded secret to sign session tokens across devices. An attacker able to obtain the distributed firmware can derive that secret and create tokens for privileged device access without legitimate credentials.

mitigation

Upgrade E3 Firmware to version 1.30. Restrict management-interface access until all devices are updated.

fixed in 1.30

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2514",
  "cve_id": "CVE-2026-92450",
  "display_id": "CVE-2026-92450",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-108550",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded JWT signing key in Kiloview E3 firmware",
  "summary": "Kiloview E3 NDI encoder firmware uses the same embedded secret to sign session tokens across devices. An attacker able to obtain the distributed firmware can derive that secret and create tokens for privileged device access without legitimate credentials.",
  "mitigation": "Upgrade E3 Firmware to version 1.30. Restrict management-interface access until all devices are updated.",
  "vendor": "Kiloview",
  "product": "E3 Firmware",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.30"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.30"
      ],
      "package_name": "E3 Firmware",
      "purl": null
    }
  ],
  "cwes": [
    798
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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": 26.9768972,
  "t0_at": "2026-10-22T22:09:58.517000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T22:09:58.517000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T22:09:58.517000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92450"
    }
  }
}

published 2026-10-22 22:33Z
last change 2026-10-22 23:45Z

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.