Plan ahead Medium Check your exposure
Phoenix Contact mGuard firewalls have StrongSwan denial-of-service flaws
CERT@VDE advisoriesPhoenix Contact, mGuard, strongSwan
What happened. CERT@VDE advisory VDE-2026-123 says multiple flaws in the StrongSwan package in affected mGuard products let unauthenticated remote attackers disrupt the StrongSwan IPsec service through denial-of-service attacks.
Who is affected. Users of Phoenix Contact FL MGUARD 2xxx and 4xxx firmware. Industrial sites using mGuard IPsec VPN for remote access are exposed, because vendors and engineers often reach plant systems through such gateways.
What to do. Check whether you run FL MGUARD 2xxx or 4xxx firmware with IPsec VPN enabled, then apply the fix listed in advisory VDE-2026-123.
When to act. Plan ahead: Firewall and VPN owners should check mGuard firmware versions at the next scheduled review; no exploitation is reported.
Editor's reading
Forasset ownerOT security lead
- Purdue level
- L5
- L3.5
Why: The mGuard is a firewall and VPN gateway at the plant boundary, placing it in the industrial DMZ and at the internet edge.
- Are you exposed?
Search your asset inventory for FL MGUARD 2xxx and 4xxx devices and check whether IPsec VPN is configured and reachable from the internet.
- If you cannot fix it yet
- Restrict IPsec connections to the mGuard to known peer addresses at the upstream firewall.
- Turn off IPsec VPN on mGuard devices that do not need it.
- Keep the mGuard management interface off untrusted networks.
- Watch for
- IPsec connection attempts from unknown addresses against the mGuard.
- Unexpected StrongSwan or IPsec service interruptions in mGuard logs.
- ATT&CK for ICS
- T0814Denial of Service
Inferred from the facts above, not stated by the source. Check it against your own site before acting.
Source: CERT@VDE advisories (opens certvde.com)
Published by Industrial Cyber Brief · Editor: Abhinav Roy · Drafted by AI and checked by code: how this is made · Corrections
More on Phoenix Contact mGuard