Mitsubishi Electric MELSEC iQ-R, Mitsubishi MELSEC SLMP, MC protocol and MELSOFT connections on standard iQ-R, iQ-F, Q and L CPUs accept device writes and Remote Stop commands from any host that can reach them unless the optional remote password is set, and on 5 February 2026 Mitsubishi Electric disclosed CVE-2025-15080, a crafted-packet flaw in SLMP on iQ-R Process CPUs. That flaw lets an unauthenticated attacker read part of the control program, write device data or cause a denial of service with a crafted SLMP or proprietary-protocol packet. Defending MELSEC networks means knowing which ports each CPU exposes, keeping firmware at the thresholds Mitsubishi publishes, and using IP filters, remote passwords and firewalls where no fix exists.he MELSOFT connection?
SLMP and MC protocol are the request-response protocols external devices use to read and write MELSEC CPU data, and the MELSOFT connection is the channel GX Works2, GX Works3 and GOT HMIs use. Mitsubishi's SLMP Reference Manual (SH-080956ENG, revision N) defines SLMP (Seamless Message Protocol) as the protocol an external device such as a PC or HMI uses to access SLMP-compatible devices over Ethernet, and adds that it allows "not only device data reading but also device data writing and resetting an SLMP-compatible device." The SLMP 3E and 4E frames are the same as the QnA-compatible 3E and 4E frames of MC protocol, so tools written for MC protocol talk to SLMP devices directly. Frames can be sent in ASCII or binary.
The MELSOFT connection is separate: it runs on fixed system ports and is what an engineering workstation uses to read, write and monitor the program. Mitsubishi's manuals list these ports as used by the system:
| Function | iQ-R CPU and Built-in Ethernet port QCPU | FX5U / FX5UC CPU (iQ-F) | Default status |
|---|---|---|---|
| MELSOFT transmission port, UDP/IP | UDP 5006 and UDP 5001 | UDP 5565 | Open |
| MELSOFT transmission port, TCP/IP | TCP 5007 | TCP 5562 | Open |
| MELSOFT direct connection | UDP 5008 | UDP 5560 | Open |
| Searching modules on the network | UDP 5009 | UDP 5561 | Open |
| Auto-open UDP port | UDP 5005 (iQ-R) | Not listed | Open |
| Web server | TCP 80 (iQ-R) | TCP 80 | Closed |
| Modbus/TCP | Not listed | TCP 502 | Closed |
| FTP server | TCP 20 and 21 | TCP 20 and 21 | Closed |
The iQ-R column comes from Appendix 11 of the MELSEC iQ-R Ethernet User's Manual (Application) (RnCPU table), the QCPU ports from Appendix 2 of the QnUCPU User's Manual (Communication via Built-in Ethernet Port), which lists the same 5001 and 5006 to 5009 numbers, and the FX5 column from Appendix 3 of the MELSEC iQ-F FX5 User's Manual (Communication), which applies to FX5U and FX5UC CPU modules. SLMP and MC protocol have no single fixed port. The engineer opens a connection and picks the CPU's own port number in the module parameters; on iQ-R the setting range is 1 to 4999 and 5010 to 65534, and on Built-in Ethernet port QCPUs 1025 to 4999 and 5010 to 65534, because 5000 to 5009 belong to the system. A capture filter on one well-known port will therefore miss SLMP traffic, and the project file is the place to find the real port list.
Key takeaways
- SLMP and MC protocol are the request-response protocols external devices use to read and write MELSEC CPU data, and the MELSOFT connection is the channel GX Works2, GX Works3 and GOT HMIs use.
- Any host that reaches an open SLMP port can read and write device memory, run and stop the CPU and read its model, unless a remote password is set.
- The MELSOFT connection carries program uploads and downloads, and its traffic is in cleartext on every MELSEC CPU series.
- MELSEC CPU advisories fall into four families: cleartext and missing authentication, weak authentication schemes, crafted-packet denial of service or code execution, and lockout abuse.
What can a host on the network do over SLMP?
Any host that reaches an open SLMP port can read and write device memory, run and stop the CPU and read its model, unless a remote password is set. The SLMP Reference Manual's command list includes:
| Command | Name | Why it matters |
|---|---|---|
| 0401 / 0403 / 0406 | Read, Read Random, Read Block (device) | Normal HMI and SCADA polling; a new reader is reconnaissance |
| 1401 / 1402 / 1406 | Write, Write Random, Write Block (device) | Changes process values and bits |
| 0613 / 1613 | Memory Read / Write | Reads and writes the buffer memory of the SLMP-compatible device |
| 1001 | Remote Run | Puts the access destination module into RUN |
| 1002 | Remote Stop | Stops program execution |
| 1006 | Remote Reset | Resets the module |
| 0101 | Read Type Name | Returns the model name and model code |
| 1630 / 1631 | Remote Password Unlock / Lock | The only credential exchange SLMP carries |
| 1810 / 1811 | Read or Search Directory/File | Lists and finds files on the CPU |
The SLMP Reference Manual also says SLMP can reach modules on other networks seamlessly through an SLMP-compatible device such as an Ethernet module, so one reachable gateway module can expose controllers behind it; the manual notes that this relay to other networks is not possible when the external device is connected to a CPU's built-in Ethernet port.
Mitsubishi's PSIRT has published the protocol-level weakness in plain terms. Advisory 2025-011 says that "MODBUS/TCP in the products does not have authentication features," so an attacker may read or write device values and stop the programs on iQ-F CPUs (CVE-2025-7405). Advisory 2025-012 says an attacker may obtain credential information by intercepting SLMP messages on iQ-F CPUs and then read or write device values and stop programs (CVE-2025-7731). Both advisories state there are no plans to release a fixed version. The same pattern applies to Modbus and OMRON FINS: network reachability is authorization.
Why is the MELSOFT engineering connection a target too?
The MELSOFT connection carries program uploads and downloads, and its traffic is in cleartext on every MELSEC CPU series. Mitsubishi's advisory 2020-003 and JPCERT/CC's JVNVU#91424496 describe cleartext communication between MELSEC iQ-R, iQ-F, Q, L and FX series CPU modules and GX Works3 or GX Works2 (CVE-2020-5594, CWE-319), with risks of eavesdropping, tampering, unauthorized operation and denial of service. All versions are affected, JVN says an update is not provided, and the only mitigation is to encrypt the path with a VPN when communicating over untrusted networks or hosts. NVD scores CVE-2020-5594 at 9.8; CISA's CSAF for ICSA-20-175-01 gives 10.0.
The MELSOFT ports have also had availability bugs. Advisory 2021-003 (CVE-2021-20591) says an attacker who does not close a connection to the MELSOFT transmission port (TCP/IP) on iQ-R CPUs keeps legitimate clients from connecting; sequence control is not affected, and if port 5007 is unused Mitsubishi suggests disabling it with the forced connection invalidation bit. A 2020 advisory (2019-005) covers the UDP side on iQ-R, iQ-F, Q, L and F series, where a flood of data can leave the MELSOFT transmission port (UDP/IP) unable to process requests. In 2025, Mitsubishi disclosed CVE-2025-3755 in iQ-F CPUs: crafted packets can read information, cause a denial of service on the MELSOFT connection used by GX Works3 and GOT, or stop the CPU, and Mitsubishi says there are no plans to release a fixed version.
Which CVE families affect MELSEC CPUs over these protocols?
MELSEC CPU advisories fall into four families: cleartext and missing authentication, weak authentication schemes, crafted-packet denial of service or code execution, and lockout abuse. The table lists the ones where SLMP, MC protocol, MELSOFT or the CPU's Ethernet port is the attack path, with Mitsubishi's CVSS, NVD's own score where NVD has analysed the record, and the CISA advisory.
| CVE | Products (per Mitsubishi) | What it allows | Vendor CVSS | NVD CVSS v3.1 | CISA advisory | Fix |
|---|---|---|---|---|---|---|
| CVE-2025-15080 | iQ-R R08/16/32/120PCPU firmware 48 and prior | Crafted SLMP or proprietary-protocol packet reads device data or part of the program, writes device data or causes DoS | 8.8 (v4.0) | Not scored (Deferred) | ICSA-26-036-02 (CISA v3.1: 9.4) | Firmware 49 |
| CVE-2025-7731 | iQ-F FX5U, FX5UC, FX5UJ, FX5S CPUs, all versions | SLMP credentials intercepted in cleartext | 7.5 | Not scored (Deferred) | ICSA-25-240-02 | None; mitigations |
| CVE-2025-7405 | iQ-F FX5U/FX5UC 1.060 and later, FX5UJ and FX5S all versions | Modbus/TCP with no authentication reads or writes device values and stops programs | 7.3 | Not scored (Deferred) | ICSA-25-240-01 | None; mitigations |
| CVE-2025-3755 | iQ-F FX5U, FX5UC, FX5UJ, FX5S CPUs, all versions | Information disclosure, MELSOFT connection DoS or CPU stop | 9.1 | Not scored (Deferred) | ICSA-25-153-03 | None; mitigations |
| CVE-2022-25155 to CVE-2022-25160 | iQ-F FX5U(C), FX5UJ; iQ-R CPUs and network modules; Q and L CPUs and Ethernet modules; all versions | Password hash accepted instead of password, weak hash, capture-replay login, cleartext storage | 5.9 to 7.4 | 5.9 to 9.1 | ICSA-22-090-04 | None; VPN, IP filter |
| CVE-2021-20599 | iQ-R Safety CPU firmware 26 and prior, SIL2 Process CPU 11 and prior | Unauthenticated login using credentials other than the password, sent in cleartext | 9.1 | 7.5 | ICSA-21-287-03 | 27 / 12; no field update |
| CVE-2021-20597 | Same Safety and SIL2 Process CPUs | Credentials sniffed when user information is registered or changed over the network | 7.4 | 9.1 | ICSA-21-250-01 | 27 / 12; no field update |
| CVE-2021-20594 | Same Safety and SIL2 Process CPUs | User-name brute force | 5.9 | 7.5 | ICSA-21-250-01 | 27 / 12; no field update |
| CVE-2023-1424 | iQ-F FX5U/FX5UC 1.220 to 1.281; iQ-R R00/01/02CPU 35 and prior, R04-R120(EN)CPU 12 to 68, SFCPU 26 to 31, PCPU 3 to 37 | Buffer overflow: DoS or malicious code execution | 10.0 | 8.1 | ICSA-23-143-03 | iQ-F 1.290; iQ-R 36, 69, 32, 38 |
| CVE-2024-0802 plus 0803, 1915, 1916, 1917 | Q03UDE, QnUDEH, QnUDV, QnUDPV (serial 26061 and prior); L02/06/26CPU(-P), L26CPU-(P)BT (26041 and prior) | Crafted packet reads arbitrary information or executes code | 9.8 each | Not scored (Deferred) | ICSA-24-074-14 | Serial 26062 / 26042; no field update |
| CVE-2025-8531 | Q03-26UDVCPU, Q04-26UDPVCPU (serial 24082 to 27081) with user authentication enabled | Integer underflow stops Ethernet and the control program | 6.8 | Not scored (Deferred) | ICSA-25-266-02 | Serial 27082; no field update |
| CVE-2020-5652 | iQ-R, Q and L CPUs (for example R04-R120(EN)CPU 52 and prior) | Crafted packet puts Ethernet into DoS until reset | 7.5 | 7.5 | ICSA-20-303-01 | Per-model thresholds |
| CVE-2021-20609, 20610, 20611 | iQ-R, Q, L CPUs and MELIPC (for example R04-R120(EN)CPU 57 and prior) | Crafted packets stop program execution or Ethernet | 7.5 each | 7.5 (20609) | ICSA-21-334-02 | Per-model thresholds |
| CVE-2025-5241 | iQ-F FX5U, FX5UC, FX5UJ, FX5S CPUs and FX5-CCLGN-MS, all versions | Repeated wrong-password logins lock legitimate users out of that port | 5.3 | Not scored (Deferred) | ICSA-25-184-04 | None; mitigations |
Three patterns stand out. First, the iQ-F CPUs carry four 2025 CVEs for which Mitsubishi lists no fix, so an FX5 on a flat network stays exposed whatever its firmware. Second, the 2022 authentication-bypass family reported by Positive Technologies (CVE-2022-25155 to 25160) covers iQ-F, iQ-R, Q and L at all versions, and in CVE-2022-25157 an eavesdropped password hash alone lets a remote attacker disclose or tamper with information in the product; Mitsubishi's advisory 2021-031 offers a VPN and the IP filter as the only countermeasures. Third, several Q/L and iQ-R Safety fixes cannot be applied to installed CPUs: the advisories say "updating the product to the fixed version is not available," and for Q/L Mitsubishi suggests moving to MELSEC iQ-R.
Vendor and NVD scores often disagree. NVD rates CVE-2021-20597 at 9.1 where Mitsubishi gives 7.4, and Mitsubishi rates CVE-2023-1424 at 10.0 where NVD gives 8.1; for CVE-2025-15080 Mitsubishi publishes CVSS v4.0 8.8 and CISA's CSAF a v3.1 score of 9.4. Every record in this guide published since March 2024 sits in NVD as Deferred, with only the vendor's score. Rank by reachability and by whether a fix can be installed, not by a single number. The KEV and EPSS prioritization guide explains how to combine these signals.
Are MELSEC CVEs exploited in the wild?
None of them is in CISA's KEV catalog. As of 2026-11-18, the CISA KEV data (catalog version 2026.11.17, 1,782 entries) has no entry with Mitsubishi Electric as the vendor. FIRST EPSS scores dated 2026-11-17 for 32 of the CVEs in this guide run from 0.0018 for CVE-2026-15688 to 0.0357 for CVE-2020-5652; CVE-2023-1424 (0.0344) and CVE-2021-20609 (0.0327) are next.
Low EPSS and no KEV entry do not make an exposed MELSEC port safe. The SLMP write and Remote Stop commands are documented functions, not exploits, and a CPU with no remote password accepts them from any host that can reach the configured port.
How do you find which MELSEC CPU firmware you are running?
Every fix threshold in the table is either a firmware version or a serial-number prefix, so the inventory needs exact model, firmware and serial per CPU. Mitsubishi uses three notations:
| Series | Version notation in advisories | Where Mitsubishi says to check |
|---|---|---|
| MELSEC iQ-R CPU modules | Two-digit firmware version, such as 48 or 49 | MELSEC iQ-R Module Configuration Manual, Appendix 1 "Checking Production Information and Firmware Version"; the Product Information List in the GX Works3 system monitor |
| MELSEC iQ-F FX5 CPU modules | Version such as 1.281 or 1.290, sometimes tied to serial number 17X**** or later | "17.3 Troubleshooting Using the Engineering Tool", module diagnostics, in the FX5S/FX5UJ/FX5U/FX5UC User's Manual (Hardware) |
| MELSEC-Q and L CPU modules | First five digits of the serial number, such as 26061 | QCPU User's Manual (Hardware Design, Maintenance and Inspection) and MELSEC-L CPU Module User's Manual, Appendix 5 "Checking Serial Number and Function Version" |
| Motion CPUs (R16/32/64MTCPU, Q17nD(S)CPU) | Operating system software version, a number or a letter | The manual for the product, per advisory 2020-013 |
A practical sequence:
Start from the GX Works2 and GX Works3 projectsand the integrator's controller list, recording the full model (R04ENCPU, FX5U-32MT/ES, Q06UDVCPU), not just the series. Read the firmware or serial from the engineering toolon an approved engineering host during an agreed window. The SLMP Read Type Name command (0101) returns only the model name and model code, so it confirms the model but not the version. Compare with the advisory notation for that seriesA Q CPU at serial 26061 is affected by the CVE-2024-0802 family, and 26062 is the fixed production. Record network modules separatelyRJ71EN71, QJ71E71-100 and LJ71E71-100 appear in CVE-2022-25155 to 25160 and CVE-2023-0457 on their own, and the FX5-EIP module has its own DoS fix, as in CVE-2026-8805 (FX5-EIP 1.000 and prior, fixed in 1.001). Track GX Works3 with the CPUsMitsubishi's advisory 2026-007 (CVE-2026-15688, CVSS v4.0 9.2) says a local attacker can bypass the GX Works3 block password; the workaround is GX Works3 1.096A or later with the project security version set to 2.
How should MELSEC networks be segmented and hardened?
Treat every MELSOFT and SLMP port as a management interface that only named engineering and HMI hosts may reach. Mitsubishi's advisories repeat the same measures, and the manuals describe the controls:
Keep MELSEC CPUs off untrusted networksUse them inside a LAN, block access from untrusted networks and hosts through a firewall, and use a VPN where internet access is required, as advisories 2025-020, 2021-008 and 2021-009 recommend. Zone the cell following the Purdue model. Turn on the IP filterOn iQ-R it is "IP filter" in section 1.13 of the iQ-R Ethernet User's Manual (Application), set under Application Settings > Security and active after a power cycle or reset; on iQ-F it is section 13.1 of the FX5 User's Manual (Communication). Allow only the engineering workstation, HMIs and SCADA servers. Mitsubishi warns that if a proxy server sits in the LAN, its address must be denied. Set a remote passwordOn FX5 CPUs it is 6 to 32 characters and, per the FX5 manual, is checked for engineering-tool, SLMP and FTP connections; the detail settings choose which user and system connections it covers. The iQ-R manual lists a lockout after failed unlocks: 1 minute at the 6th error, 5 at the 7th, 15 at the 8th and 60 minutes from the 9th. That lockout is itself a denial-of-service lever, as CVE-2025-5241 shows on iQ-F, and CVE-2025-7731 shows iQ-F SLMP credentials travel in cleartext, so the remote password is an access gate, not encryption. Close ports you do not useIn iQ-R Transmission Port Settings, each MELSOFT UDP and TCP port and the auto-open UDP port can be set to "Not Use"; Built-in Ethernet port QCPUs have a disable-using-port setting. Leave the web server at its default "Not Use" unless needed, which also avoids CVE-2020-5666 on iQ-R CPUs. Register users and change passwords over USBon iQ-R Safety and SIL2 Process CPUs, as Mitsubishi's advisory for CVE-2021-20597 recommends, and enable GX Works3's enhanced vulnerability-management mode for user information where advisory 2023-021 lists the versions. Block writes in RUN on QCPUs where you canThe QnUCPU built-in Ethernet manual says that when "Enable online change (FTP, MC Protocol)" is disabled, a data write request to a CPU in RUN is refused with a NAK. Protect project filesCVE-2023-0457 says FTP and web server credentials are stored in plaintext in project files for iQ-F, iQ-R, Q and L, so encrypt projects when sharing them. Restrict physical accessto the CPUs, panels, switches and engineering PCs, a mitigation in every 2025 Mitsubishi advisory cited here, and patch to the fixed versions where the advisory says an update is available.
The IEC 62443-3-3 system requirements give the zone-and-conduit language for documenting these controls, and the same approach applies to the CC-Link IE TSN networks behind many iQ-R and iQ-F CPUs.
How do you monitor SLMP and MELSOFT traffic?
Monitoring starts with a baseline of which hosts talk to which MELSEC ports. Because SLMP ports are chosen per project, collect them from the parameters first, then watch flows:
- Any host other than a known engineering workstation, HMI or SCADA server opening TCP 5007 or 5562, or sending to UDP 5006, 5001, 5008 or 5565.
- Module-search traffic to UDP 5009 or 5561 from an unfamiliar host, the MELSEC equivalent of a network scan.
- New TCP or UDP flows to the configured SLMP ports, especially from outside the cell or the engineering zone.
- Repeated short connections to a MELSOFT port, the pattern behind the CVE-2021-20591 and CVE-2025-5241 availability issues.
- Any MELSEC port reachable across a zone boundary toward the business network or the internet.
For command-level detail, such as a Remote Stop (1002) or a device write (1401), you need a parser that decodes SLMP; flow records alone show only who connected to which port and when. Map what you see to MITRE ATT&CK for ICS techniques such as Change Operating Mode and Program Download when you write alert rules.
Worked example: what does a MELSEC review of one assembly cell find?
Synthetic example, not a real plant. A cell has two R04ENCPU controllers, three FX5U-64MT/ES CPUs, one Q06UDVCPU, a GOT HMI and one engineering laptop.
| Observation | Why it matters | Action |
|---|---|---|
| Both R04ENCPU at firmware 66 | In the CVE-2023-1424 range (12 to 68) | Update to firmware 69 or later |
| FX5U CPUs at 1.270 | In the CVE-2023-1424 range (1.220 to 1.281); CVE-2025-7731 and 3755 have no fix | Update to 1.290; IP filter to HMI and laptop only |
| Q06UDVCPU serial 25112 | Affected by the CVE-2024-0802 family, no field update | Isolate behind a firewall; plan migration to iQ-R |
| TCP 5007 and 5562 reachable from the office VLAN | Unauthenticated, cleartext engineering access (CVE-2020-5594) | Firewall to the engineering laptop; VPN for remote work |
| No remote password on any CPU | SLMP writes and Remote Stop accepted from any reachable host | Set remote passwords on SLMP and MELSOFT connections |
| GX Works3 1.090U on the laptop | Below the 1.096A workaround for CVE-2026-15688 | Update and set project security version 2 |
How can SoftWSP help with MELSEC exposure?
A passive capture shows who talks to MELSEC ports without touching a running controller. SoftWSP's OT Snapshot reads Zeek and ICSNPP logs from a mirror-port recording and builds a host-by-port inventory, including hosts using ports such as 5007 or 5562, and lists remote-access sessions (SSH, Telnet, RDP, VNC) that cross from outside the private address range. It has no SLMP, MC protocol or MELSOFT decoder, so this traffic shows at connection level only, without commands or device addresses. For a controller list, Device & Firmware Security identifies models and versions and matches them against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories. An engineer reviews every AI-drafted, cited report before it is sent.
What are the common pitfalls?
- Assuming SLMP is safe because it uses a custom port; the port is in the project file, and module search on 5009 or 5561 helps an attacker find CPUs.
- Treating the remote password as encryption; it controls access, while CVE-2025-7731 and CVE-2020-5594 show the traffic is cleartext.
- Firewalling TCP 5007 and forgetting UDP 5006, 5001 and 5008, or the different FX5 ports 5560 to 5565.
- Waiting for a firmware update for iQ-F CVE-2025-7731, 7405 or 3755, where Mitsubishi lists none.
- Reading Q/L serial numbers as firmware versions, or comparing iQ-R and iQ-F version numbers with the wrong threshold.
- Updating CPUs but leaving GX Works3 and network modules at affected versions.
This guide draws on Mitsubishi Electric PSIRT advisories 2019-005, 2020-003, 2020-013, 2020-015, 2021-003, 2021-008 to 2021-011, 2021-019, 2021-031, 2022-023, 2023-003, 2023-021, 2023-024, 2025-003, 2025-005, 2025-011 to 2025-014, 2025-020 and 2026-007; Mitsubishi's SLMP Reference Manual, MELSEC iQ-R Ethernet User's Manual (Application), MELSEC iQ-F FX5 User's Manual (Communication) and QnUCPU built-in Ethernet manual; CISA CSAF advisories; JPCERT/CC JVNVU#91424496; and NVD records. KEV and EPSS facts are as of 2026-11-18. It is general information, not a substitute for Mitsubishi Electric's product-specific advisories or a current search for your exact hardware and firmware version.
Put this guide to work
Frequently asked questions
Does SLMP or MC protocol have authentication?
Not by default. Mitsubishi Electric's SLMP Reference Manual describes SLMP as the protocol an external device such as a PC or HMI uses to read and write device data and to reset an SLMP-compatible device, and its command list includes Remote Run (1001), Remote Stop (1002) and Remote Reset (1006). The 3E and 4E frames are the same as the QnA-compatible 3E and 4E frames of the older MC protocol. The only access check the CPU applies is the optional remote password: per the MELSEC iQ-F FX5 User's Manual (Communication), it is checked for engineering-tool, SLMP and FTP connections when a remote password is set. Mitsubishi's own manuals say the remote password and the IP filter do not completely prevent unauthorized access, and CVE-2025-7731 shows that on iQ-F CPUs the credential information in SLMP messages can be intercepted in cleartext.
Which ports do MELSEC PLCs use for MELSOFT and SLMP?
On MELSEC iQ-R CPU modules and Built-in Ethernet port QCPUs, Mitsubishi's manuals list UDP 5006 and 5001 as MELSOFT transmission ports, TCP 5007 as the MELSOFT transmission port for TCP/IP, UDP 5008 for MELSOFT direct connection and UDP 5009 for searching modules on the network. On FX5U and FX5UC CPU modules (MELSEC iQ-F), the same functions sit on UDP 5560 (direct connection), UDP 5561 (module search), TCP 5562 (MELSOFT TCP/IP) and UDP 5565 (MELSOFT UDP/IP), and Modbus/TCP on 502 is closed by default. SLMP and MC protocol have no single fixed port: the engineer assigns the CPU's own port number per connection, from 1 to 4999 or 5010 to 65534 on iQ-R and from 1025 to 4999 or 5010 to 65534 on Built-in Ethernet port QCPUs, because 5000 to 5009 are reserved by the system. Inventory the configured ports from the project, not from a port list.
Are any Mitsubishi MELSEC CVEs in the CISA KEV catalog?
No. As of 2026-11-18, the CISA Known Exploited Vulnerabilities catalog (version 2026.11.17, 1,782 entries) has no entry with Mitsubishi Electric as the vendor, so none of the MELSEC CVEs in this guide is listed. FIRST EPSS scores dated 2026-11-17 for 32 of the CVEs discussed here range from 0.0018 for CVE-2026-15688 to 0.0357 for CVE-2020-5652. Absence from KEV says little about SLMP exposure: reading and writing device data or stopping the CPU over SLMP needs no exploit when no remote password is set and the port is reachable.
How do I check the firmware version of a MELSEC CPU?
It depends on the series, and Mitsubishi's advisories name the method. For iQ-R CPU modules, the advisories point to Appendix 1, Checking Production Information and Firmware Version, in the MELSEC iQ-R Module Configuration Manual; the firmware version (for example 48 or 49) is shown in the Product Information List of the GX Works3 system monitor. For iQ-F FX5 CPUs, they point to module diagnostics in the engineering tool, as described in section 17.3 of the FX5S/FX5UJ/FX5U/FX5UC Hardware manual; versions look like 1.281 or 1.290. For MELSEC-Q and L CPUs, the advisories use the first five digits of the serial number, such as 26061 or 26062, and the QCPU and L CPU hardware manuals explain where to read it. SLMP's Read Type Name command (0101) returns only the model name and model code, not the firmware version.
Can every vulnerable MELSEC CPU be patched?
No. Several advisories end with mitigations only. Mitsubishi says there are no plans to release a fixed version for the iQ-F CVE-2025-7731 (SLMP credential interception), CVE-2025-7405 (Modbus/TCP with no authentication) and CVE-2025-3755 (crafted packets on the MELSOFT connection). For the MELSEC-Q/L CVE-2024-0802 family and for the iQ-R Safety CPU CVE-2021-20599, fixed firmware exists in newer production, but Mitsubishi states that updating an existing product to the fixed version is not available and suggests migrating Q/L systems to MELSEC iQ-R. CVE-2020-5594, cleartext communication between CPUs and GX Works2/GX Works3, affects all versions and its only mitigation is a VPN over untrusted networks. For these, the IP filter, remote password, firewalling and physical access control are the defence.
Sources
- Mitsubishi Electric: Vulnerability Information (PSIRT advisory index)
- Mitsubishi Electric Security Advisory 2025-020: Information Disclosure, Information Tampering, and DoS in Mitsubishi Electric proprietary protocol communication and SLMP communication (5 February 2026; CVE-2025-15080)
- Mitsubishi Electric Security Advisory 2025-012: Information Disclosure Vulnerability in MELSEC iQ-F Series CPU module (28 August 2025; CVE-2025-7731)
- Mitsubishi Electric Security Advisory 2025-011: MELSEC iQ-F Series CPU module, Modbus/TCP missing authentication (28 August 2025; CVE-2025-7405)
- Mitsubishi Electric Security Advisory 2025-003: Information Disclosure and DoS in MELSEC iQ-F Series CPU module (29 May 2025; CVE-2025-3755)
- Mitsubishi Electric Security Advisory 2021-031: Authentication Bypass, Information Disclosure and Information Tampering in Multiple FA Products (updated 31 May 2022; CVE-2022-25155 to CVE-2022-25160)
- Mitsubishi Electric Security Advisory 2021-011: Authentication Bypass in MELSEC iQ-R Series Safety CPU/SIL2 Process CPU Module (updated 18 April 2024; CVE-2021-20599)
- Mitsubishi Electric Security Advisory 2023-003: DoS and Remote Code Execution in MELSEC Series CPU module (updated 25 April 2024; CVE-2023-1424)
- Mitsubishi Electric Security Advisory 2023-024: Information Disclosure and RCE in MELSEC-Q/L Series CPU Module (updated 13 June 2024; CVE-2024-0802, CVE-2024-0803, CVE-2024-1915, CVE-2024-1916, CVE-2024-1917)
- Mitsubishi Electric Security Advisory 2020-003: Cleartext communication between MELSEC CPU modules and GX Works3/GX Works2 (23 June 2020; CVE-2020-5594)
- Mitsubishi Electric Security Advisory 2021-003: DoS in MELSOFT Transmission Port (TCP/IP) (27 May 2021; CVE-2021-20591)
- Mitsubishi Electric Security Advisory 2026-007: Password Authentication Bypass in GX Works3 and Motion Control Setting (17 September 2026; CVE-2026-15688)
- Mitsubishi Electric: SLMP Reference Manual, SH-080956ENG revision N (PDF)
- Mitsubishi Electric: MELSEC iQ-R Ethernet User's Manual (Application), SH-081257ENG revision AG (PDF)
- Mitsubishi Electric: MELSEC iQ-F FX5 User's Manual (Communication), SH-082625ENG revision K (PDF)
- Mitsubishi Electric: QnUCPU User's Manual (Communication via Built-in Ethernet Port), SH-080811ENG revision Y (PDF)
- CISA CSAF: ICSA-26-036-02 Mitsubishi Electric MELSEC iQ-R Series (CVE-2025-15080)
- CISA CSAF: ICSA-25-240-02 Mitsubishi Electric MELSEC iQ-F Series CPU Module (CVE-2025-7731)
- CISA CSAF: ICSA-22-090-04 Mitsubishi Electric FA Products (CVE-2022-25155 to CVE-2022-25160)
- CISA CSAF: ICSA-23-143-03 Mitsubishi Electric MELSEC Series CPU module, Update D (CVE-2023-1424)
- CISA CSAF: ICSA-24-074-14 Mitsubishi Electric MELSEC-Q/L Series, Update B (CVE-2024-0802 family)
- JPCERT/CC JVNVU#91424496: Mitsubishi Electric MELSEC iQ-R, iQ-F, Q, L, and FX series vulnerable to cleartext transmission of sensitive information (CVE-2020-5594)
- NVD: CVE-2025-15080 (MELSEC iQ-R Process CPU, SLMP and proprietary protocol)
- NVD: CVE-2025-7731 (MELSEC iQ-F SLMP credential interception)
- NVD: CVE-2023-1424 (MELSEC iQ-F/iQ-R CPU buffer overflow)
- NVD: CVE-2022-25157 (MELSEC password hash used for authentication)
- CISA Known Exploited Vulnerabilities catalog (data mirror on GitHub)
- FIRST: Exploit Prediction Scoring System (EPSS)
About this guide
SoftWSP OT/ICS Desk
Covers the OT/ICS security cluster: 71 guides.

In this cluster
Questions about this page?
