CVE-2026-35018
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 · uneditedNetComm NF20MESH routers running firmware R6B031 and earlier contain an authenticated remote code execution vulnerability that allows authenticated attackers to execute arbitrary commands as root by injecting shell metacharacters into the username JSON parameter processed by the dalStorage_addUserAccount function. Attackers can exploit the unsafe concatenation of user-supplied input into a shell command string passed to rut_doSystemAction without sanitization to achieve full root-level command execution on the underlying operating system.
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 confidenceAuthenticated remote code execution vulnerability in NetComm NF20MESH routers (firmware R6B031 and earlier). The dalStorage_addUserAccount function insecurely concatenates user-supplied input from the username JSON parameter into a shell command passed to rut_doSystemAction, allowing authenticated attackers to inject shell metacharacters and achieve root-level command execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm device model is NetComm NF20MESHAccess the router web interface or check the device label/marketing materials to verify the exact model number matches NF20MESHAffected if Device is a NetComm NF20MESH router
-
Check installed firmware versionLog into the router web interface and navigate to the status or firmware upgrade page to view the current firmware version. Alternatively, check via CLI if available using 'cat /proc/version' or router-specific commandsAffected if Firmware version is R6B031 or any version earlier than R6B031 (e.g., R6B030, R6B029, etc.)
-
Verify if remote web administration is enabledAccess the router administration panel, go to remote management settings, and check whether remote access (WAN-facing HTTP/HTTPS administration) is enabledAffected if Remote administration interface is exposed to the WAN or untrusted networks
-
Check authentication configurationReview the router user account settings to determine if default credentials are in use or if weak/user-managed passwords are set for administrative accessAffected if The device allows authenticated access with any valid credentials, enabling the attacker to reach the vulnerable function
The device is affected if it is a NetComm NF20MESH router running firmware R6B031 or earlier, and the attacker can obtain valid admin credentials to access the device either locally or remotely.
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.
From vendor dataApply available firmware updates from NetComm. If no update is available, disable remote administration interfaces, enforce strict access controls, and segment affected devices from untrusted networks to reduce attack surface.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35018 — 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-35018 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