Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-10271: MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computa

64
This week
CRITICAL 9.8REMOTEUPGRADEUPGRADEUPGRADE

CVE-2020-10271 is a critical-severity flaw (CVSS 9.8) affecting mir100 firmware, mir200 firmware, mir250 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computational graph to all network interfaces, wireless and wired. This is the result of a bad set up and can be mitigated by appropriately configuring ROS and/or applying custom patches as appropriate. Currently, the ROS computational graph can be accessed fully from the wired exposed ports. In combination with other flaws such as CVE-2020-1026

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.8% (top 22%)
CISA exploited listNo
WeaknessCWE-668
Published2020-06-24
Last modified2026-06-17
Publisher (CNA): Alias Robotics S.L. · Vendor: aliasrobotics · mobile-industrial-robotics

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

aliasrobotics mir100 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
aliasrobotics mir200 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
aliasrobotics mir250 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
aliasrobotics mir500 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
aliasrobotics mir1000 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
mobile-industrial-robotics er200 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-10271?

mir100 firmware: upgrade to newer than 2.8.1.1; mir200 firmware: upgrade to newer than 2.8.1.1; mir250 firmware: upgrade to newer than 2.8.1.1. Exact commands for each OS are on this page.

Is CVE-2020-10271 being exploited?

CVE-2020-10271 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-10271 affect?

CVE-2020-10271 affects mir100 firmware, mir200 firmware, mir250 firmware. Severity is critical (CVSS 9.8). MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computational graph to all network interfaces, wireless and wired. This is the result of a bad set up and can be mitigated by appropriate

How urgent is CVE-2020-10271?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.