Skip to main content
Menu
CVEs

Moxa EDS-510E Series signature verification bypass in switch firmware updates

Affects Moxa EDS-510E Series switches on all firmware versions, with a CVSS score of 8.6 (high). The advisory names no fixed version or patch, and gives a firmware checksum check as the workaround.

CVE-2026-130494EUVD-2026-130913GHSA-3265-727J-HX45Published November 20, 2026, updated

8.6HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

Moxa EDS-510E Series Ethernet switches do not verify firmware signatures, so an attacker with administrative privileges can install unauthorized firmware and potentially run arbitrary code on the device. The attacker reaches the device remotely over the network but must first log in with administrative access.

Written by a model

Original description

An improper firmware authenticity verification vulnerability exists in the affected Ethernet Switches products. An authenticated remote attacker with administrative privileges could exploit the lack of cryptographic signature verification to install unauthorized firmware, potentially leading to arbitrary code execution on the affected device.

Who should check

Teams running Moxa EDS-510E Series Ethernet switches on any firmware version, where an authenticated administrator can reach the device over the network.

“EDS-510E Series”

moxa.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects EDS-510E Series switches on all firmware versions.
  2. Workaround: Verify the firmware file's integrity with the SHA-512 checksum from the Moxa product page before updating the firmware.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130494 (An improper firmware authenticity verification vulnerability exists in the affected Ethernet Switches products.), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130494 (entry last updated 2026-11-20):
Affected:
- Moxa EDS-510E Series: versions 1.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects EDS-510E Series switches on all firmware versions. (source: https://www.moxa.com/en/support/product-support/security-advisory/mpsa-268140-cve-2026-130493,-cve-2026-130494-multiple-vulnerabilities-in-ethernet-switches)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
Workaround: Verify the firmware file's integrity with the SHA-512 checksum from the Moxa product page before updating the firmware. (source: https://www.cve.org/CVERecord?id=CVE-2026-130494)
CISA KEV: CVE-2026-130494 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130494 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.moxa.com/en/support/product-support/security-advisory/mpsa-268140-cve-2026-130493,-cve-2026-130494-multiple-vulnerabilities-in-ethernet-switches
- https://www.cve.org/CVERecord?id=CVE-2026-130494
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130494
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130494"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 30 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorymoxa.com · en/support/product-support/security-advisory/mpsa-268140-cve-2026-130493,-cve-2026-130494-multiple-vulnerabilities-in-ethernet-switches
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130494
RecordNVD · CVE-2026-130494

Questions about CVE-2026-130494

Is CVE-2026-130494 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The switch does not properly verify that its firmware is authentic. An attacker can install unauthorized firmware, which could lead to arbitrary code execution on the device.

Source: moxa.com, cve.org

Which versions are affected by CVE-2026-130494?

EDS-510E Series: version 1.0.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory lists the EDS-510E Series on all firmware versions, with no version range given. To check a device, look at the firmware version it reports in its management interface and compare it with the product's documentation.

Source: moxa.com, cve.org

How do I fix CVE-2026-130494?

The advisory names no fixed firmware version or patch ID. Until one is published, verify each firmware file's SHA-512 checksum against the value on the Moxa product page before updating.

Source: moxa.com, cve.org

What if there's no patch?

Verify the firmware file's integrity with the SHA-512 checksum from the Moxa product page before updating the firmware. The advisory gives no other workaround.

Source: moxa.com, cve.org

No corrections so far. Something wrong on this page? Report an error.