# CVE-2026-111548: A stack-based buffer overflow vulnerability exists in the web management interface of affected Moxa wireless device servers.


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-92hr-hqpf-3392

## What is CVE-2026-111548?

CVE-2026-111548 is a medium-severity vulnerability in Moxa NPort W2150A-W4/W2250A-W4 Series, published on 27 Oct 2026. 

### Official description

A stack-based buffer overflow vulnerability exists in the web management interface of affected Moxa wireless device servers. An authenticated remote attacker with low privileges could exploit insufficient bounds checking of user-supplied input, causing the web management service to become unresponsive. Restoring the service requires power cycling the affected device, while other device functions remain operational.

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

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


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

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

## Is CVE-2026-111548 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111548 is a medium-severity vulnerability in Moxa NPort W2150A-W4/W2250A-W4 Series, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111548 in the wild and no public exploit code.

Affected product: Moxa NPort W2150A-W4/W2250A-W4 Series. 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-111548/ (Markdown: https://insights.sbomify.com/CVE-2026-111548/index.md)
```

## Sources

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

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