# CVE-2026-25823: Memory corruption in n/a

> Unauthenticated attackers can trigger a stack buffer overflow in HMS Networks Ewon Flexy and Cosy+ devices, leading to remote code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-7p64-f72w-3rpr

## What is CVE-2026-25823?

CVE-2026-25823 is a critical memory corruption vulnerability in n/a, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HMS Networks Ewon Flexy with firmware before 15.0s4, Cosy+ with firmware 22.xx before 22.1s6, and Cosy+ with firmware 23.xx before 23.0s3 have a stack buffer overflow that leads to a Denial of Service, which can also be exploited to achieve Unauthenticated Remote Code Execution.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-25823?


## How do I fix CVE-2026-25823?

No fix has been published for CVE-2026-25823 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25823 being exploited?

There is no known exploitation of CVE-2026-25823 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25823 and fix it if it is affected.

What it is: CVE-2026-25823 is a critical memory corruption vulnerability in n/a, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25823 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25823/ (Markdown: https://insights.sbomify.com/CVE-2026-25823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25823
- OSV: https://osv.dev/vulnerability/CVE-2026-25823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25823/
Summaries are generated and may contain mistakes; the official description above is the record.