Skip to main content
CVE-2025-8748VulnerabilityPublished Updated

CVE-2025-8748: Mobile Industrial Robots MiR Robots · OS Command Injection

Affects Mobile Industrial Robots MiR RobotsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mobile Industrial Robots MiR RobotsAffected
  • =0
Fixed in–

AI-suggested

1. Upgrade MiR robot software to version 3.0.0 or later as soon as the patch becomes available from the vendor. 2. Until patches are applied, restrict authenticated access to MiR robot management interfaces strictly to trusted personnel and devices, using network segmentation and firewall rules. 3. Implement strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of credential compromise. 4. Monitor network traffic to and from MiR robots for unusual or unauthorized command patterns indicative of exploitation attempts. 5. Conduct regular audits of user accounts with access to MiR robots and remove unnecessary privileges. 6. Employ intrusion detection systems tailored to industrial control systems to detect anomalous activities. 7. Collaborate with the vendor for timely updates and security advisories. 8. Incorporate secure coding and input validation practices in any custom integrations with MiR robots to prevent injection flaws.

Description

MiR software versions prior to version 3.0.0 are affected by a command injection vulnerability. A malicious HTTP request crafted by an authenticated user could allow the execution of arbitrary commands on the underlying operating system.

References

Community reviews

Loading reviews…