CVE-2026-1874Always-Incorrect Control Flow Implementation vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET/IP Ethernet Module FX5-ENET/IP versions 1.106 and prior and Mitsubishi Electr…
Updated under an hour ago ()
Does this affect you?
It affects mitsubishielectric melsec_iq-f_fx5-eip_firmware and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
Always-Incorrect Control Flow Implementation vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET/IP Ethernet Module FX5-ENET/IP versions 1.106 and prior and Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-EIP EtherNet/IP Module FX5-EIP versions 1.000 and prior allows a remote attacker to cause a denial-of-service (DoS) condition on the products by continuously sending UDP packets to the products. A system reset of the product is required for recovery.
- CVSS
- 7.5 HIGH (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-670
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jun 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
mitsubishielectric melsec_iq-f_fx5-eip_firmware mitsubishielectric:melsec_iq-f_fx5-eip_firmware | through 1.000 | NVD |
mitsubishielectric melsec_iq-f_fx5-enet/ip_firmware mitsubishielectric:melsec_iq-f_fx5-enet/ip_firmware | through 1.106 | NVD |
References
- https://jvn.jp/vu/JVNVU93286687/third-party-advisory
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-62-01third-party-advisory
- https://www.mitsubishielectric.com/psirt/vulnerability/pdf/2025-021_en.pdfvendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.