CVE Intelligence
Medium Memory corruption

CVE-2026-111548 — Stack-based Buffer Overflow in Moxa NPort W2150A-W4/W2250A-W4 Series

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.

Published Oct 27, 2026 · Updated Oct 27, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Moxa

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+4
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.34%
ahead of 28% of scored CVEs · Oct 29, 2026
Affects
Moxa
NPort W2150A-W4/W2250A-W4 Series
CVSS base
5.3
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Moxa NPort W2150A-W4/W2250A-W4 Series).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Moxa NPort W2150A-W4/W2250A-W4 Series ≥ 1.0 and ≤ 1.5 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Scope
X
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
None
Availability (vulnerable system)
Low
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — psirt@moxa.com via NIST National Vulnerability Database
5.3 CVSS 4.0 Medium — — Moxa via CVE Program (cve.org) e CISA ADP
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: psirt@moxa.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-121 · Stack-based Buffer Overflow

Other CVEs with this weakness →

EPSS over time FIRST

Oct 28, 2026 → Oct 29, 2026 · 2 reading(s) · max 0.34%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 27, 2026 · NIST National Vulnerability Database
  • Affected products added · moxa/nport w2150a-w4/w2250a-w4 series
    Oct 27, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 27, 2026
  • CVSS changed · 5.3
    Oct 27, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 27, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 27, 2026 · Alertas do Telegram
  • CVE published
    Oct 27, 2026 · Moxa

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 27, 2026 – Oct 27, 2026
  • 1× Official description updated · Oct 27, 2026 – Oct 27, 2026

References

1 on the record

Elsewhere on this site

Moxa
every CVE for this vendor
Memory corruption
same class
CWE-121
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-10829 Stack-based Buffer Overflow in Moxa NPort W2150A-W4/W2250A-W4 Series Jun 16, 2026
  • CVE-2026-10828 Use of Externally-Controlled Format String in Moxa NPort W2150A-W4/W2250A-W4 Series Jun 16, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-111548 is "Stack-based Buffer Overflow in Moxa NPort W2150A-W4/W2250A-W4 Series", rated Medium. It affects NPort W2150A-W4/W2250A-W4 Series (Moxa); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.34% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.