CVE-2026-112360

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

GHSA-4wqx-c3pj-5r3f ↗EUVD-2026-104647 ↗

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.
Netis EAP930 1.250905.115454
ETK-2026-2417Zero's internal tracking ID, independent of the CVE number., permanent identifier
35msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+61h06m
0
+2h
+4h
+6h
+8h
+10h

description

Netis EAP930 firmware 1.250905.115454 is affected by a backdoor-related flaw in its debug CGI endpoint. An attacker who already has the required high-privilege access may be able to remotely create unauthorized access through that interface.

mitigation

Restrict device management and CGI access to trusted administrative networks and accounts, and remove the interface from internet exposure. Apply a vendor firmware update when one is published; no fixed version is identified in the available evidence.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2417",
  "cve_id": "CVE-2026-112360",
  "display_id": "CVE-2026-112360",
  "ghsa_id": "GHSA-4wqx-c3pj-5r3f",
  "euvd_id": "EUVD-2026-104647",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Backdoor vulnerability in Netis EAP930 debug CGI endpoint",
  "summary": "Netis EAP930 firmware 1.250905.115454 is affected by a backdoor-related flaw in its debug CGI endpoint. An attacker who already has the required high-privilege access may be able to remotely create unauthorized access through that interface.",
  "mitigation": "Restrict device management and CGI access to trusted administrative networks and accounts, and remove the interface from internet exposure. Apply a vendor firmware update when one is published; no fixed version is identified in the available evidence.",
  "vendor": "Netis",
  "product": "EAP930",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.250905.115454"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "EAP930",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/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": 26.321602433333332,
  "t0_at": "2026-10-19T21:30:19.739000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T21:30:19.739000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T21:30:19.739000+00:00",
      "url": "https://github.com/advisories/GHSA-4wqx-c3pj-5r3f"
    }
  }
}

published 2026-10-22 10:10Z
last change 2026-10-22 10: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.