Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

HMS Ewon Flexy and Cosy+ remote-access gateway vulnerabilities: Talk2M, HMS advisories, fixed firmware and hardening

Last updated:

HMS Networks' Ewon Flexy and Ewon Cosy+ are industrial remote-access gateways that machine builders and plant teams install next to a PLC so that engineers can reach it through HMS's Talk2M cloud service and a VPN. Their main risks are old firmware, a web interface reachable from the WAN and credentials sent without encryption. HMS's March 2026 advisory lists four CVEs, including an unauthenticated stack buffer overflow it rates 9.5, fixed in Flexy and Cosy 131 firmware 15.0s4 and Cosy+ firmware 22.1s6 and 23.0s3. As of 2026-11-22 no Ewon CVE is in CISA's KEV catalog. Securing them means current firmware, the web interface reached only through Talk2M, unique credentials and a segmented machine network.

Key takeaways

  • HMS Networks' Ewon Flexy and Ewon Cosy+ are industrial remote-access gateways that machine builders and plant teams install next to a PLC so that engineers can reach it through HMS's Talk2M cloud service and a VPN.
  • An Ewon gateway sits between a machine network and the outside world.
  • Talk2M is built on outbound connections.
  • HMS advisory HMSSAR-2026-03-09-001, released on 9 March 2026 and revised on 13 March 2026 to correct a CVSS vector and add the Cosy 131, thanks Nicolas Schaff and the VOC EDF team for reporting the flaws on the Flexy.

What are Ewon Flexy and Cosy+ and how does Talk2M fit in?

An Ewon gateway sits between a machine network and the outside world. HMS's best practices for a secure usage of the Ewon solution describe the model: combined with Talk2M, Ewon gateways give remote access to equipment installed on their LAN side, a Talk2M account manages the devices, users and security settings, and engineers connect with the Talk2M client eCatcher. HMS advises one gateway per machine or system and warns against using one gateway to open access to a whole factory network.

CISA's advisories on these products list deployment in commercial facilities, critical manufacturing, energy, water and wastewater, and food and agriculture, worldwide, with HMS Networks headquartered in Sweden. In practice it is a box in a machine's control cabinet that a machine builder's service engineer uses to reach a PLC or HMI behind it.

HMS's advisories name these product lines, and the firmware lines differ:

Product line Firmware line in HMS advisories Fix for the March 2026 CVEs
Ewon Flexy (10x and 20x, such as the Flexy 202 and 205) 14.x and 15.x 15.0s4 or later
Ewon Cosy 131 14.x and 15.x, same numbering as the Flexy 15.0s4 or later
Ewon Cosy+ 21.x, 22.x and 23.x 22.1s6 or later on 22.xx; 23.0s3 or later on 23.xx
eCatcher (engineer's PC client) 6.x and 7.x Separate advisories, see below

HMS's Radio Equipment Directive advisory HMSSAR-2025-07-09-001 names Flexy and Cosy firmware 15.0s0 and Cosy+ firmware 23.0s0 as the releases for the EU requirements that apply from 1 August 2025, and says that gateways still in distributor stock may carry older firmware. Update a newly delivered gateway before installing it.

How are Ewon gateways reached on the network?

Talk2M is built on outbound connections. HMS's Talk2M help page Which port(s) should I open in my firewall says the services "use only outbound connections", that "there are no inbound connections from the Talk2m Servers", and that the firewall needs to open only two outbound ports, UDP 1194 and TCP 443. A gateway used only through Talk2M therefore needs no port forward and no public address.

The gateway's web configuration interface (GUI) is the other path. HMS's March 2026 advisory recommends blocking access to the GUI on the WAN and says that this is the default from firmware 15.0 onwards; its February 2025 advisory says the WAN interface is protected by default. Anyone who opens the GUI on the WAN, or leaves an older unit configured that way, exposes the flaws listed below to whoever can reach that address. The BOD 23-02 guide on internet-exposed management interfaces explains how to confirm exposure from outside rather than from the configuration.

HMS's February 2025 advisory also points to an HMS support article on blocking all unused Flexy and Cosy 131 services on the LAN, WAN and VPN interfaces. Use it to switch off every service you do not need on each interface.

Which vulnerabilities did HMS publish in 2026?

HMS advisory HMSSAR-2026-03-09-001, released on 9 March 2026 and revised on 13 March 2026 to correct a CVSS vector and add the Cosy 131, thanks Nicolas Schaff and the VOC EDF team for reporting the flaws on the Flexy. HMS says its internal analysis showed that the Cosy+ is also affected.

CVE Flaw, per HMS HMS score (CVSS v4.0) CISA ADP score on NVD (CVSS v3.1)
CVE-2026-25823 Stack buffer overflow leading to denial of service, which HMS says can also be exploited for unauthenticated remote code execution 9.5 9.8
CVE-2026-25817 OS command injection allowing remote code execution by an attacker with low-privilege credentials on the gateway 9.4 8.8
CVE-2026-25819 Specially crafted HTTP request reboots the device; needs access to the GUI, no credentials 8.7, "when the GUI is exposed to the network" 7.5
CVE-2026-25818 Weak entropy for authentication cookies; with a stolen session cookie an attacker can brute-force the user password 6.9 9.1

HMS lists the affected ranges as all Flexy and Cosy 131 firmware before 15.0s4, all Cosy+ firmware before 22.1s6, and Cosy+ 23.0s0 to 23.0s2. The CVE descriptions on NVD give the same fixes and name Flexy and Cosy+ but not the Cosy 131, which HMS added in its revision. The scores disagree in both directions: CISA's ADP rates the cookie flaw 9.1 where HMS gives 6.9 because HMS assumes an adjacent attacker who already holds a stolen cookie. Prioritize on the unauthenticated CVE-2026-25823 and CVE-2026-25819 first if the GUI is reachable from anywhere other than the engineering network.

What were the Cosy+ findings HMS published in 2024?

HMS advisory HMSSAR-2024-07-29-001, released on 29 July 2024, thanks Moritz Abrell of SySS for six findings. Five are in Cosy+ firmware 21.x before 21.2s10 and 22.x before 22.1s3; the sixth was in the Talk2M service.

CVE Flaw, per HMS and NVD HMS score (CVSS v4.0) NVD score (CVSS v3.1)
CVE-2024-33892 Information leakage through cookies 7.4 7.5 (CISA ADP 5.3)
CVE-2024-33896 (see our advisory) Code injection due to improper parameter blacklisting 3.3 7.2
CVE-2024-33893 Cross-site scripting when displaying the logs 2.1 6.1
CVE-2024-33895 One key encrypts the configuration parameters on every device; since 21.2s10 and 22.1s3 the key is unique per device 4.4 6.6
CVE-2024-33894 Several processes run with elevated privileges; HMS says "this is not an issue" but recommends upgrading 1.0 CISA ADP 8.8 only
CVE-2024-33897 (see our advisory) A compromised Cosy+ could request a certificate signing request from Talk2M for another device, causing an availability issue none given 9.1

HMS's fix is Cosy+ firmware 21.2s10 or 22.1s3; CVE-2024-33897 was patched on the Talk2M production server on 18 April 2024 and needs no action on the gateway. The gap between HMS's low v4.0 scores and NVD's higher v3.1 scores is large for the code injection and privileged process findings. A Cosy+ that is current for the 2026 advisory (22.1s6 or 23.0s3) is also past these fixes.

Which advisories cover credentials sent in clear text?

Two recent CVEs are about passwords on the wire, both reported by researchers of the CoE-CNDS Lab at VJTI, Mumbai.

  • CVE-2024-7755. CISA's ICSA-24-291-04 of 17 October 2024 says the Ewon Flexy 202 "transmits credentials using a weak encoding method base64", so an attacker on the network can sniff and decode them. CISA lists firmware 14.2s0 and scores it 8.2 (CVSS v3.1) and 7.1 (CVSS v4.0). HMS's advisory HMSSAR-2024-10-22-001 applies it to all Flexy 10x and 20x and recommends firmware 14.9s3 or later, while CISA names 14.9s2. Use HMS's 14.9s3, or the 15.0s4 that the 2026 advisory needs anyway.
  • CVE-2025-0432. CISA's ICSA-25-023-06 of 23 January 2025 says the Flexy 202 sends user credentials in clear text when a user is added or credentials are changed through its web page, scored 5.7 (CVSS v3.1) by CISA and HMS. HMS's advisory HMSSAR-2025-02-07 extends it to Cosy and Flexy on all firmware versions. It is reachable from the LAN, or from the WAN when the GUI is reachable there unprotected, and "NOT possible when using the VPN interface and Talk2m". No firmware fix is listed; HMS asks owners to connect to the GUI only through the VPN interface and Talk2M once the gateway is installed, to block unused ports and to lock the gateway and its LAN in a cabinet.

Which older Ewon vulnerabilities still matter?

The older advisories matter mostly for gateways that have sat untouched in a machine for years.

Advisory CVEs Affected and fixed Scores
CISA ICSA-20-254-03 (10 September 2020) and HMS HMSSAR-2020-09-11-001, reported by Parth Srivastava of Protiviti India CVE-2020-16230 permissive CORS policy with wildcards Flexy and Cosy before 14.1; fix 14.1 CISA, HMS and NVD 2.3 (v3.1)
CISA ICSA-20-098-03 (7 April 2020), reported by Ander Martínez of Titanium Industrial Security through INCIBE CVE-2020-10633 reflected cross-site scripting that can initiate a password change eWON Flexy and Cosy before 14.1s0; fix 14.1s0 CISA and NVD 6.1 (v3.1)
CISA ICSA-15-351-03 (2015) CVE-2015-7924 to CVE-2015-7929: session not cleared at log-off, CSRF, missing access control on I/O server requests, XSS, password autocomplete, sensitive data in GET requests eWON firmware before 10.1s0, per NVD and the CISA CSAF; CISA says most are fixed by updating to the newest version NVD v3.0: 9.9 for CVE-2015-7926, 8.8 for 7924, 8.5 for 7928 (CISA CSAF 9.3), 8.0 for 7925
NVD only, CNA CyberDanube CVE-2024-9154 authenticated code injection giving system-level command execution Flexy 205 through 14.8s0 CyberDanube 8.6 (v4.0)
NVD only, CNA VulnCheck CVE-2019-25470 authentication bypass through the wsdReadForm endpoint, exposing user passwords protected only by a hard-coded XOR key eWON firmware 12.2 to 13.0 VulnCheck 8.7 (v4.0), 7.5 (v3.1)

For CVE-2024-9154 there is no HMS advisory. CyberDanube's report records that HMS called it low priority because firmware update permissions already allow a downgrade and rooting, and CyberDanube recommends upgrading to the latest firmware. CVE-2019-25470 is a hard-coded key problem of the kind covered in the guide to hard-coded credentials in embedded firmware.

HMS's advisory HMSSAR-2020-10-14-001 says that the Cosy 141 and the CD series use the Treck TCP/IP stack but that HMS's analysis with Nviso found them not affected by Ripple20.

What about Talk2M and eCatcher?

Talk2M is a cloud service HMS runs, and HMS publishes advisories when it is affected. In HMSSAR-2026-10-22-001, released on 22 October 2026, HMS says the PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 did not affect the Flexy, Cosy+, eCatcher or eBuddy, which do not use PHP. For the Talk2M services, including Remote Access, M2Web and DataMailbox, affected PHP versions were patched on 21 October 2026 or removed, and HMS found no indicators of compromise on the servers using PHP. The 2024 certificate signing request flaw CVE-2024-33897 was also fixed on the server side. Owners cannot patch Talk2M themselves; what they control is the Talk2M account, its users and its permissions.

eCatcher runs on the engineer's Windows PC and opens the VPN tunnel, so its flaws reach the remote-access chain from the other end:

Advisory CVE Affected, per HMS, CISA or NVD Score
HMS HMSSAR-2026-11-12-001 (12 November 2026) CVE-2026-114820, compromised eMudhra CA certificates in the bundled Java runtime, allowing man-in-the-middle eCatcher before 7.1.2; fixed in 7.1.2 HMS 9.1 (v3.1)
HMS HMSSAR-2024-10-15-001 CVE-2024-27903, OpenVPN plug-ins on Windows loadable from any directory eCatcher before 7.0.3 HMS 9.8 (v3.1)
CISA ICSA-20-210-03 (28 July 2020), reported by Sharon Brizinov of Claroty CVE-2020-14498 stack-based buffer overflow allowing remote code execution eCatcher before 6.5.5; fix 6.5.5 or later CISA 9.6, NVD 10.0 (v3.1)
HMS advisory 2021-07-09-001, as referenced by NVD CVE-2021-33214 weak filesystem permissions eCatcher through 6.6.4, per NVD NVD 6.1 (v3.1)

eCatcher wraps OpenVPN, so the version tracking in the OpenVPN and strongSwan guide applies to the engineering PCs as well as to the gateways.

Are Ewon vulnerabilities exploited in the wild?

No exploitation is on record in CISA's catalog. As of 2026-11-22 the KEV catalog (catalog version 2026.11.20, 1,790 entries) has no entry for HMS Networks, Ewon, Cosy, Talk2M or eCatcher. CISA's ICSA-24-291-04 and ICSA-25-023-06 both say that "no known public exploitation specifically targeting this vulnerability has been reported to CISA at this time". Neither HMS nor CISA names an actor targeting Ewon gateways.

FIRST EPSS scores dated 2026-11-21, the latest as of 2026-11-22:

CVE EPSS Percentile
CVE-2024-33896 0.04023 0.908
CVE-2020-14498 0.03984 0.908
CVE-2015-7926 0.03397 0.891
CVE-2015-7928 0.03249 0.886
CVE-2026-25817 0.00920 0.612
CVE-2026-25823 0.00825 0.583
CVE-2024-9154 0.00640 0.516
CVE-2026-25819 0.00561 0.475
CVE-2024-7755 0.00299 0.230
CVE-2026-25818 0.00159 0.051
CVE-2025-0432 0.00144 0.037

All are below 5 percent. The Cosy+ code injection, the 2020 eCatcher overflow and the 2015 eWON flaws score highest; the 2026 remote code execution flaws sit in the middle. A low EPSS score says little about a gateway whose GUI is open on the WAN, so rank by reachability first, as the KEV and EPSS prioritization guide explains.

How do you check which firmware an Ewon gateway runs?

Fixes arrive per product line, so record the line before comparing numbers:

  1. Record the productIn HMS's advisories, Flexy and Cosy 131 use the 14.x and 15.x numbering and Cosy+ uses 21.x, 22.x and 23.x, so a version that does not fit the product's line means the inventory needs checking.
  2. Record the full firmware version, including the "s" buildThe fixes are 15.0s4, 22.1s6, 23.0s3, 21.2s10 and 22.1s3, so "15.0" alone is not enough.
  3. Compare against each advisoryFor a Flexy or Cosy 131, 15.0s4 or later clears the 2026 advisory and the older 14.1, 14.1s0 and 14.9s3 fixes. For a Cosy+, 22.1s6 or 23.0s3 clears the 2026 and 2024 advisories.
  4. Record the eCatcher version on every engineering PCAt least 7.1.2 for the eMudhra certificates, which also clears 7.0.3 and 6.5.5.
  5. Record what is enabledGUI access on the WAN, services on the LAN, WAN and VPN interfaces, port forwards to devices behind the gateway, and whether the VPN is always on or switched by a key switch.
  6. Do not rely on CPE matching aloneCVE records such as CVE-2024-33892 and CVE-2026-25817 were assigned by MITRE with no product data ("n/a") and carry CISA ADP enrichment, so read the HMS advisory for the affected lines, as the IEC 62443-2-3 patch management guide describes for vendor-tracked patching.

How should Ewon gateways be hardened?

The measures below come from HMS's advisories and best practices document and from CISA's ICSA-20-254-03, ICSA-24-291-04 and ICSA-25-023-06:

  1. Update firmwareFlexy and Cosy 131 to 15.0s4 or later, Cosy+ to 22.1s6 or 23.0s3 or later, and check HMS's cybersecurity page for anything newer. Update eCatcher to 7.1.2 or later.
  2. Reach the GUI only through Talk2MHMS says to connect to the GUI only through the VPN interface and Talk2M once the gateway is installed, which also removes the clear-text exposure of CVE-2025-0432. CISA's ICSA-20-254-03 adds: do not publicly expose the WAN IP of the devices, and use the WAN firewall built into all Ewon devices.
  3. Block unused servicesFollow HMS's support article on blocking unused Flexy and Cosy 131 services on the LAN, WAN and VPN interfaces.
  4. Use unique users, strong passwords and two-factor authenticationHMS's best practices say not to use default credentials, to define a strong password for the gateway's configuration page, to create one Talk2M user per person, to set password policies and expiry, and to enable two-factor authentication for all users. The hard-coded credentials guide explains why shared and factory passwords fail.
  5. Limit who can reach whatUse Talk2M user groups and device pools so most users are standard users limited to specific gateways or devices, keep users disabled until they need to work, and delete leavers immediately, as HMS advises.
  6. Give the site control of the tunnelHMS suggests wiring a key switch to a digital input to enable or disable the VPN locally, and an indicator light on a digital output that shows when a remote connection is active.
  7. Segment and lockOne gateway per machine, never a gateway into the whole plant network, as HMS advises; CISA asks owners to keep control system devices off the internet, behind firewalls isolated from business networks. HMS adds a locked cabinet with tamper seals for the gateway and its LAN. Zone the machine network with the Purdue model.

How do you monitor Ewon gateways?

Start with a baseline of what each gateway talks to, then alert on changes:

  • Outbound traffic from the gateway on UDP 1194 or TCP 443 to destinations other than the Talk2M servers in HMS's published list.
  • Any inbound connection from the internet to the gateway's WAN address, or to a port forwarded to a PLC behind it.
  • A gateway rebooting unexpectedly after inbound HTTP requests, which fits CVE-2026-25819 and CVE-2026-25823.
  • Logins to the GUI from the LAN outside a scheduled maintenance window, and Talk2M connection reports showing users or hours that do not match your service schedule, which HMS recommends reviewing regularly.

Flow records show who connected to which port and when, not what happened inside the VPN tunnel. Map alerts to MITRE ATT&CK for ICS techniques, such as external remote services.

Worked example: what does a review of machine gateways find?

Synthetic example, not a real site. A packaging plant has six machines from three builders, each with a builder-supplied Ewon gateway.

Observation Why it matters Action
Three Flexy 205 units on 14.8s0 Below 15.0s4 for the 2026 advisory and below 14.9s3 for CVE-2024-7755 Update to 15.0s4 or later with the builders
One Flexy with the GUI open on the WAN through the plant firewall CVE-2026-25823 and CVE-2026-25819 need only GUI access Close the forward; use Talk2M only
Two Cosy+ units on 22.1s3 Clear of the 2024 findings, below 22.1s6 for the 2026 advisory Update to 22.1s6, or 23.0s3 as HMS suggests
One gateway wired into the plant backbone rather than a machine network Remote users can reach far more than one machine Move it behind the machine's own segment
A builder's engineers share one Talk2M login, eCatcher 7.0.1 on their laptops No accountability, and below 7.0.3 and 7.1.2 Ask the builder for named users with two-factor authentication and current eCatcher

Where does passive monitoring fit in an Ewon review?

A passive capture shows who talks to the gateways and the machines behind them without logging in to anything. SoftWSP's OT Snapshot reads Zeek and ICSNPP logs from a mirror-port recording and builds a host-by-port inventory at connection level, including gateways sending UDP 1194 or TCP 443 to the internet, and lists remote-access sessions (SSH, Telnet, RDP, VNC) that cross from outside the private address range. It does not read Ewon firmware versions, Talk2M settings or what happens inside the VPN tunnel, so those come from the asset list. For that list, Device & Firmware Security identifies components 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. Ewon gateways sit at the same network edge as the routers in the Teltonika guide and the Sierra Wireless AirLink guide, and the OT security guide for small manufacturers shows where machine-builder remote access fits in a wider programme.

What are the common pitfalls?

  • Treating the gateway as the machine builder's problem; it sits on your network and HMS's fixes need someone to install them.
  • Reading "15.0" as fixed when the 2026 advisory needs 15.0s4.
  • Applying Flexy version numbers to a Cosy+, which uses the 22.x and 23.x lines.
  • Opening the GUI on the WAN "temporarily" for a builder, which exposes the unauthenticated 2026 flaws.
  • Changing passwords through the GUI over the LAN, which CVE-2025-0432 sends in clear text, instead of over Talk2M.
  • Sharing one Talk2M account across a builder's whole service team.
  • Updating gateways but leaving eCatcher on engineering laptops below 7.1.2.

This guide draws on HMS Networks' security advisories HMSSAR-2026-03-09-001, HMSSAR-2024-07-29-001, HMSSAR-2024-10-22-001, HMSSAR-2025-02-07, HMSSAR-2025-07-09-001, HMSSAR-2026-10-22-001, HMSSAR-2026-11-12-001, HMSSAR-2024-10-15-001, HMSSAR-2020-09-11-001 and HMSSAR-2020-10-14-001; HMS's best practices document and Talk2M help pages; CISA ICS advisories ICSA-24-291-04, ICSA-25-023-06, ICSA-20-254-03, ICSA-20-098-03, ICSA-20-210-03 and ICSA-15-351-03 and their CSAF records; NVD records; CyberDanube's report; the CISA KEV catalog; and FIRST EPSS data. KEV and EPSS facts are as of 2026-11-22. It is general information, not a substitute for HMS's advisories or a check of your exact product and firmware.

Put this guide to work

Frequently asked questions

Which firmware fixes the 2026 Ewon Flexy and Cosy+ vulnerabilities?

HMS security advisory HMSSAR-2026-03-09-001, first released on 9 March 2026 and revised on 13 March 2026, covers CVE-2026-25817, CVE-2026-25818, CVE-2026-25819 and CVE-2026-25823. HMS tells owners to update every Flexy to firmware 15.0s4 or later, Cosy+ units on the 22.xx line to 22.1s6 or later and Cosy+ units on the 23.xx line to 23.0s3 or later. Its revision added the Cosy 131, which is affected before 15.0s4 like the Flexy. HMS also suggests that Cosy+ owners on 22.1s6 consider moving to 23.0s3.

What did the 2024 Cosy+ research find?

HMS advisory HMSSAR-2024-07-29-001 thanks Moritz Abrell of SySS for six findings in Cosy+ firmware, CVE-2024-33892 to CVE-2024-33897. They include information leakage through cookies, code injection through improper parameter blacklisting, cross-site scripting in the log view, one shared key used to encrypt configuration parameters on every device, and processes running with elevated privileges. HMS fixed them in Cosy+ firmware 21.2s10 and 22.1s3, where the configuration key became unique per device. The sixth, CVE-2024-33897, let a compromised Cosy+ request a certificate signing request from Talk2M for another device; HMS patched that on the Talk2M production server on 18 April 2024.

Is an Ewon vulnerability in the CISA KEV catalog?

No. As of 2026-11-22 the CISA Known Exploited Vulnerabilities catalog (version 2026.11.20, 1,790 entries) has no entry for HMS Networks, Ewon, Cosy, Talk2M or eCatcher. CISA's advisories for CVE-2024-7755 and CVE-2025-0432 say that no known public exploitation specifically targeting those vulnerabilities had been reported to CISA. That does not make an exposed gateway safe: HMS rates the unauthenticated stack buffer overflow CVE-2026-25823 at 9.5 (CVSS v4.0).

Which ports does an Ewon gateway need for Talk2M?

HMS's Talk2M help says the service uses only outbound connections and that the site firewall needs to open only two outbound ports, UDP 1194 and TCP 443. There are no inbound connections from the Talk2M servers, so no port forward to the gateway is needed for Talk2M remote access. HMS's Talk2M onsite firewall page notes that the server list changes as servers are added, and points to its cloud server status page for notifications.

Are Ewon credentials sent in clear text?

Two advisories cover credentials in transit. CVE-2024-7755: CISA's ICSA-24-291-04 says the Ewon Flexy 202 encodes credentials only with base64, so anyone on the network path can decode them; HMS applies it to all Flexy 10x and 20x and fixes it in firmware 14.9s3 or later, while CISA names 14.9s2. CVE-2025-0432: HMS says Cosy and Flexy on all firmware versions send credentials in clear text when a user is added or a password is changed through the web page, and that this cannot be exploited over the VPN interface and Talk2M. HMS's mitigation is to reach the gateway's web interface only through the Talk2M VPN once it is installed, block unused services and keep the gateway in a locked cabinet.

Sources

  1. HMS Networks: Cybersecurity and security advisories page
  2. HMS Security Advisory HMSSAR-2026-03-09-001: Ewon Flexy, Cosy 131 and Ewon Cosy+ several vulnerabilities
  3. HMS Security Advisory HMSSAR-2024-07-29-001: Several vulnerabilities affecting the Cosy+ product line
  4. HMS Security Advisory HMSSAR-2024-10-22-001: Flexy 10x and 20x insufficiently protected credentials
  5. HMS Security Advisory HMSSAR-2025-02-07: Recommendations to protect the Ewon gateways credentials
  6. HMS Security Advisory HMSSAR-2025-07-09-001: Radio Equipment Directive and Ewon products
  7. HMS Security Advisory HMSSAR-2026-10-22-001: Talk2M, Flexy and Ewon Cosy+ PHP vulnerabilities
  8. HMS Security Advisory HMSSAR-2026-11-12-001: eMudhra compromised certificates in Ecatcher
  9. HMS Security Advisory HMSSAR-2024-10-15-001: OpenVPN vulnerability in Ecatcher
  10. HMS Security Advisory HMSSAR-2020-09-11-001: Ewon devices (CVE-2020-16230)
  11. HMS Security Advisory HMSSAR-2020-10-14-001: Ewon Cosy 141 and CD series (Ripple20)
  12. HMS Networks: Best practices for a secure usage of the Ewon solution
  13. Ewon online help: Which port(s) should I open in my firewall to allow connection to Talk2m?
  14. Ewon online help: Talk2m onsite firewall requirements
  15. CISA: ICSA-24-291-04 HMS Networks EWON FLEXY 202
  16. CISA CSAF: ICSA-24-291-04 HMS Networks EWON FLEXY 202
  17. CISA: ICSA-25-023-06 HMS Networks Ewon Flexy 202
  18. CISA CSAF: ICSA-25-023-06 HMS Networks Ewon Flexy 202
  19. CISA CSAF: ICSA-20-254-03 HMS Networks Ewon Flexy and Cosy
  20. CISA CSAF: ICSA-20-098-03 HMS Networks eWON Flexy and Cosy
  21. CISA CSAF: ICSA-20-210-03 HMS Industrial Networks eCatcher
  22. CISA CSAF: ICSA-15-351-03 eWON Vulnerabilities
  23. NVD: CVE-2026-25823 (Ewon Flexy and Cosy+ stack buffer overflow)
  24. NVD: CVE-2026-25817 (Ewon Flexy and Cosy+ OS command injection)
  25. NVD: CVE-2024-33896 (Cosy+ code injection)
  26. NVD: CVE-2024-33897 (Talk2M certificate signing request issue)
  27. NVD: CVE-2024-7755 (Ewon Flexy 202 weakly encoded credentials)
  28. NVD: CVE-2024-9154 (Ewon Flexy 205 code injection, CyberDanube)
  29. NVD: CVE-2019-25470 (eWON firmware wsdReadForm authentication bypass)
  30. NVD: CVE-2021-33214 (eCatcher weak filesystem permissions)
  31. CyberDanube: Authenticated Remote Code Execution in Ewon Flexy 205
  32. CISA Known Exploited Vulnerabilities catalog
  33. FIRST: Exploit Prediction Scoring System (EPSS)
Was this guide helpful?

In this cluster

HMS Ewon Flexy and Cosy+ remote-access gateway vulnerabilities: Talk2M, HMS advisories, fixed firmware and hardening