CVE-2026-4622
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 · uneditedOS Command Injection vulnerability in NEC Platforms, Ltd. Aterm Series allows a attacker to execute arbitrary OS commands via network.
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 · high confidenceOS Command Injection vulnerability in NEC Aterm Series network devices allows unauthenticated remote attackers to execute arbitrary OS commands via the network interface, potentially compromising the entire device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.7.2< 1.6.0< 1.5.0< 1.4.2< 1.4.2< 1.3.2< 2.5.0< 1.3.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify your NEC Aterm device modelLocate the model name on the device physical label, or log into the web management interface and check the status or device information pageAffected if The device model is one of: Wg2600hs, Wf1200cr, Wg1200cr, Wg2600hp4, Wg2600hm4, Wg2600hs2, Wx3000hp, or Wx3000hp2
-
Determine the installed firmware versionAccess the device web administration panel, usually at 192.168.0.1 or 192.168.1.1, and navigate to the firmware or system information section to view the current versionAffected if The firmware version is below: 1.7.2 for Wg2600hs, 1.6.0 for Wf1200cr, 1.5.0 for Wg1200cr, 1.4.2 for Wg2600hp4/Wg2600hm4, 1.3.2 for Wg2600hs2/Wx3000hp2, or 2.5.0 for Wx3000hp
-
Verify network exposure of management interfaceCheck your router firewall rules, NAT port forwarding settings, or the device network configuration to determine if HTTP/HTTPS management ports are accessible from outside the local networkAffected if The device management interface (ports 80/443 or equivalent) is reachable from untrusted networks such as the WAN or internet
You are affected if you are running any of the listed NEC Aterm models with a firmware version below the specified threshold AND the management interface is exposed to the network.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped1.3.21.4.21.5.0
Apply vendor firmware updates when available; until then, restrict network access to management interfaces and implement network segmentation to limit exposure.
Upgrade to Aterm firmware >= 1.7.2 (Wg2600hs), >= 1.6.0 (Wf1200cr), >= 1.5.0 (Wg1200cr), >= 1.4.2 (Wg2600hp4/Wg2600hm4), >= 1.3.2 (Wg2600hs2/Wx3000hp2), or >= 2.5.0 (Wx3000hp) depending on model
- 1. Identify the exact Aterm model number from the affected device
- 2. Navigate to the official NEC support website (jpn.nec.com) or NEC Aterm product support page
- 3. Locate the firmware download section for the specific model
- 4. Download the latest firmware version: Wg2600hs version 1.7.2 or later, Wf1200cr version 1.6.0 or later, Wg1200cr version 1.5.0 or later, Wg2600hp4 version 1.4.2 or later, Wg2600hm4 version 1.4.2 or later, Wg2600hs2 version 1.3.2 or later, Wx3000hp version 2.5.0 or later, Wx3000hp2 version 1.3.2 or later
- 5. Access the router's web management interface via HTTP/HTTPS
- 6. Navigate to the firmware update or administration section
- 7. Upload the downloaded firmware file and initiate the update
- 8. Wait for the update to complete and the device to reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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