VulnerabilityPublished 12 Mar 2026Updated 13 Mar 2026

CVE-2026-25819: Uncontrolled Resource Consumption

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2026-25819, organizations should first ensure that Ewon Flexy and Cosy+ devices are not directly exposed to untrusted networks, including the internet. Network segmentation and firewall rules should restrict access to the device management interfaces to trusted personnel and systems only. Employ VPNs or secure tunnels for remote access to the devices to reduce exposure. Monitor network traffic for unusual HTTP requests targeting device GUIs that could indicate exploitation attempts. Although no official patches are currently linked, organizations should stay alert for firmware updates from HMS Networks addressing this vulnerability and apply them promptly once available. Additionally, implement device hardening best practices such as disabling unnecessary services and changing default credentials to reduce attack surface. Regularly audit device configurations and access logs to detect and respond to suspicious activity quickly. In critical environments, consider redundant monitoring paths or failover mechanisms to maintain visibility during potential device reboots.

Description

CVE-2026-25819 is a high-severity vulnerability affecting HMS Networks Ewon Flexy and Cosy+ devices with certain firmware versions. It allows unauthenticated attackers to cause a denial of service by sending a specially crafted HTTP request to the device's GUI, triggering a reboot. No authentication or user interaction is required, and the attack can be executed remotely over the network. The vulnerability impacts device availability but does not compromise confidentiality or integrity. Exploitation requires network access to the device's management interface. There are no known exploits in the wild yet, and no patches have been linked at this time. Organizations relying on these industrial communication devices should prioritize mitigation to prevent operational disruptions. This vulnerability is particularly relevant for industries using Ewon devices for remote monitoring and control.

Impact

The primary impact of CVE-2026-25819 is denial of service, which can cause operational disruptions in industrial environments relying on Ewon Flexy and Cosy+ devices for remote monitoring and control. A forced reboot interrupts communication and data collection, potentially leading to loss of visibility into critical systems, delayed response to operational issues, and downtime. In environments where continuous monitoring is essential for safety or process control, such disruptions could have cascading effects, including safety risks or production losses. Since the attack requires no authentication and can be executed remotely, the risk is elevated if devices are exposed to untrusted networks or the internet. However, the vulnerability does not allow data theft or manipulation, limiting its impact to availability. Organizations with large deployments of these devices, especially in manufacturing, energy, and critical infrastructure sectors, face increased risk of operational interruptions and associated financial and reputational damage.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:42 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats