CVE-2026-110825

validatingZero is analyzing and reversing it now.
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-306 Missing Authentication for Critical Function
ETK-2026-2513Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Kiloview E3 firmware before 1.30 does not enforce authentication for certain ONVIF network and time configuration changes. A remote attacker can change device naming, DNS resolvers, or time sources when the ONVIF service is reachable, potentially supporting later interception or certificate-validation attacks.

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

mitigation

Upgrade Kiloview E3 Firmware to version 1.30 or later. Until upgraded, restrict access to the ONVIF service to trusted management networks.

fixed in 1.30

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2513",
  "cve_id": "CVE-2026-110825",
  "display_id": "CVE-2026-110825",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Missing authentication in Kiloview E3 ONVIF configuration service",
  "summary": "Kiloview E3 firmware before 1.30 does not enforce authentication for certain ONVIF network and time configuration changes. A remote attacker can change device naming, DNS resolvers, or time sources when the ONVIF service is reachable, potentially supporting later interception or certificate-validation attacks.",
  "mitigation": "Upgrade Kiloview E3 Firmware to version 1.30 or later. Until upgraded, restrict access to the ONVIF service to trusted management networks.",
  "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": [
    306
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-22T22:11:55.815000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T22:11:55.815000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T22:11:55.815000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110825"
    }
  }
}

published 2026-10-22 22:32Z
last change 2026-10-22 22:41Z

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.