CVE-2026-43845

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

GHSA-rvm7-jmf3-hgwj ↗EUVD-2026-104846 ↗

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-2146Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 29msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+25h24m
0
+2h
+4h
+6h
+8h
+10h

description

ADAM-3600 devices using vulnerable firmware contain a weakness in password-reset handling. An attacker may be able to bypass authentication; the available evidence does not state the required access or interaction conditions.

mitigation

Update ADAM-3600 firmware to version 2.8.5.0 or later. Until updates are complete, limit access to device management and password-reset interfaces to trusted administrators and networks.

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.34%25th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 08:48Z
Δ 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:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2146",
  "cve_id": "CVE-2026-43845",
  "display_id": "CVE-2026-43845",
  "ghsa_id": "GHSA-rvm7-jmf3-hgwj",
  "euvd_id": "EUVD-2026-104846",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in ADAM-3600 password reset",
  "summary": "ADAM-3600 devices using vulnerable firmware contain a weakness in password-reset handling. An attacker may be able to bypass authentication; the available evidence does not state the required access or interaction conditions.",
  "mitigation": "Update ADAM-3600 firmware to version 2.8.5.0 or later. Until updates are complete, limit access to device management and password-reset interfaces to trusted administrators and networks.",
  "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.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0034,
  "epss_percentile": 0.2591,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.92980575,
  "t0_at": "2026-10-20T08:48:28.456000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T08:48:28.456000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T08:48:28.456000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-43845"
    }
  }
}

published 2026-10-20 09:13Z
last change 2026-10-21 14:33Z

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.