CVE-2026-43836

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

GHSA-7wv5-vcx2-7h34 ↗EUVD-2026-104831 ↗

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.
Advantech ADAM-3600 prior to version 2.8.5.0
ETK-2026-2142Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 04msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+24h49m
0
+2h
+4h
+6h
+8h
+10h

description

Advantech ADAM-3600 devices are affected by a command-injection issue in network-packet handling. An attacker able to send a forged packet to an affected device may execute commands with maximum privileges.

mitigation

Limit network access to affected devices to trusted management hosts and isolate them from untrusted networks. Check Advantech’s security advisory for an update or vendor-provided remediation; no fixed version is recorded 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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.60%47th percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 08:08Z
Δ 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-20 08:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2142",
  "cve_id": "CVE-2026-43836",
  "display_id": "CVE-2026-43836",
  "ghsa_id": "GHSA-7wv5-vcx2-7h34",
  "euvd_id": "EUVD-2026-104831",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Forged-packet command injection in Advantech ADAM-3600",
  "summary": "Advantech ADAM-3600 devices are affected by a command-injection issue in network-packet handling. An attacker able to send a forged packet to an affected device may execute commands with maximum privileges.",
  "mitigation": "Limit network access to affected devices to trusted management hosts and isolate them from untrusted networks. Check Advantech’s security advisory for an update or vendor-provided remediation; no fixed version is recorded in the available evidence.",
  "vendor": "Advantech",
  "product": "ADAM-3600",
  "affected": [
    {
      "affected_notes": [
        "prior to version 2.8.5.0"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ADAM-3600",
      "purl": null
    }
  ],
  "cwes": null,
  "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": 0.006,
  "epss_percentile": 0.4779,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.663920983333334,
  "t0_at": "2026-10-20T08:08:19.495000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T08:08:19.495000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T08:08:19.495000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-43836"
    }
  }
}

published 2026-10-20 08:35Z
last change 2026-10-21 10:15Z

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.