How do I check whether I am affected by CVE-2026-43844?

Check the EdgeLink image version on each ADAM-3600 (device web UI or firmware info). Anything before 2.8.5.0 is affected. Also check whether TCP ports 6001 and 7001 are reachable from untrusted networks, for example with nmap -p 6001,7001 .

What is the fix for CVE-2026-43844?

Update ADAM-3600 EdgeLink firmware to 2.8.5.0 or later (Advantech support page, ADAM-3600-C2G EdgeLink Image). Until then, keep the device off the internet and firewall ports 6001/7001 and the web interface to trusted hosts. Note: the Advantech firmware page I saw listed 2.8.5.0 as Beta, so confirm the release channel.

Who is not affected by CVE-2026-43844?

Not affected if: firmware-2.8.5.0-or-later, not-network-reachable.

Live › vulnerability › CVE-2026-43844

Go to dashboard

critical9.3Other

Unnamed proprietary protocol lets attackers bypass authentication entirely

Advantech ADAM-3600 EdgeLink remote terminal unit (industrial data acquisition) has an authentication bypass on its proprietary protocol, CVSS 4.0 9.3, network reachable, no privileges needed. Vendor says the cause is a singleton pattern that mixes up commands between TCP ports 6001 and 7001, which differ in what they implement. Found by Nozomi Networks (Simone Bossi, Raffaele Bova). Disclosed to vendor 2026-04-29, patched 2026-10-15, public 2026-10-20. Not known to be exploited.

Summary written from the sources below. Check the originals before acting.

CVSS 4.0

9.3

critical

scored by 5f57b9bf-260d-4433-bf07-b6a79e9bb7d4

known so far5 of 6

missing: exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is critical, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker bypasses login to reach protected protocol functions.
CVSS said: 9.3. The facts above say high; we keep the sources' critical until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-43844

Go to dashboard

critical9.3Other

Unnamed proprietary protocol lets attackers bypass authentication entirely

Summary written from the sources below. Check the originals before acting.

CVSS 4.0

9.3

critical

scored by 5f57b9bf-260d-4433-bf07-b6a79e9bb7d4

known so far5 of 6

missing: exploitation

First public: Oct 20, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is critical, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker bypasses login to reach protected protocol functions.
CVSS said: 9.3. The facts above say high; we keep the sources' critical until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Unnamed proprietary protocol lets attackers bypass authentication entirely

Why it is critical, and not just CVSS

Who is affected

Know the next one before it finds you.

Unnamed proprietary protocol lets attackers bypass authentication entirely

Why it is critical, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources