dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-10829

HIGH · 8.6 CVSS v4.0 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stack-based buffer overflow vulnerability has been found in the NPort W2150A-W4/W2250A-W4 Series version 1.5 and earlier. This vulnerability stems from insufficient input validation of user-supplied input in the "Server location" parameter on the Basic settings page. An attacker could exploit this vulnerability by sending crafted input to the web service, resulting in memory corruption. Successful exploitation of this vulnerability could allow remote code execution on the target system with root privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stack-based buffer overflow exists in the web interface of NPort W2150A-W4/W2250A-W4 Series devices (version 1.5 and earlier) due to insufficient input validation on the 'Server location' parameter within the Basic settings page. By sending specially crafted input to this parameter, an attacker can overwrite stack memory, leading to memory corruption and potentially achieving remote code execution with root privileges.

MitigationApply vendor-supplied firmware updates when released; until then, restrict network access to the device's web management interface to trusted sources only and disable remote management if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the device web interface and navigate to the System Information or Status page to view the model number and firmware version. Alternatively, check the device label or documentation.
    Affected if The device is a NPort W2150A-W4 or W2250A-W4 series with firmware version 1.5 or earlier
  2. Verify web interface is accessible
    Attempt to access the device web interface by entering its IP address in a web browser. Confirm the login page loads.
    Affected if The web interface is reachable on the network, indicating exposure to potential exploitation
  3. Confirm remote management is enabled
    Log into the web interface and navigate to the Network or Administration settings section. Look for options related to 'Remote Management', 'Web Management', or 'HTTP/HTTPS Access'. Check if remote access is enabled.
    Affected if Remote management or web interface access is enabled, allowing unauthenticated or authenticated attackers to reach the vulnerable 'Server location' parameter
  4. Assess network exposure to untrusted sources
    Review firewall rules, ACLs, or network segmentation surrounding the device. Determine if the web interface IP is accessible from outside the trusted network or the internet.
    Affected if The device web interface is exposed to untrusted network segments or the internet, increasing exploitability

The device is affected if it is an NPort W2150A-W4 or W2250A-W4 with firmware version 1.5 or earlier AND its web interface with the 'Server location' parameter is accessible from a network path an attacker could traverse.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates when released; until then, restrict network access to the device's web management interface to trusted sources only and disable remote management if not required.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10829 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data