CVE-2026-38703
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 · uneditedA command injection vulnerability exists in the ZeroTier VPN feature of InHand Networks IR302 firmware V3.5.108, IR305 firmware V1.0.118, IR315 firmware V1.0.118, IR615 firmware V1.0.118, and earlier versions. Attackers can exploit this vulnerability to obtain ROOT privileges on remote target devices.
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 confidenceA command injection vulnerability exists in the ZeroTier VPN feature of multiple InHand Networks IR series industrial router firmware versions (IR302 V3.5.108, IR305/IR315/IR615 V1.0.118 and earlier). The vulnerability allows unauthenticated remote attackers to inject arbitrary commands through the VPN feature, achieving ROOT privilege escalation on affected devices.
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.0.121< 3.5.112< 1.0.121< 1.0.121CVSS 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 device modelLog into the router web interface or check the device label to confirm the exact model (IR302, IR305, IR315, or IR615)Affected if Device is any of these four models
-
Check installed firmware versionAccess the router administration panel, typically found under 'System' > 'Firmware Version' or 'Device Info' in the web interface. Alternatively, use the command line and run 'cat /etc/version' or 'ver' if accessible.Affected if Firmware version is below 3.5.112 for IR302, or below 1.0.121 for IR305/IR315/IR615
-
Verify ZeroTier VPN statusIn the router web interface, navigate to 'VPN' > 'ZeroTier' or 'Network' > 'ZeroTier VPN' to check if the feature is configured or enabled.Affected if ZeroTier VPN feature is enabled or configured on the device
-
Confirm vulnerability applicabilitySince this is a command injection flaw in the ZeroTier VPN component, the device is only vulnerable if ZeroTier VPN is actively in use. Check for any ZeroTier network memberships or client configurations.Affected if ZeroTier VPN is enabled and the firmware version falls within the affected ranges
The device is affected if it is an IR302, IR305, IR315, or IR615 model running firmware below the fixed version (3.5.112 for IR302, 1.0.121 for others) AND the ZeroTier VPN feature is enabled or configured.
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.0.1213.5.112
Apply available firmware updates from InHand Networks that address this vulnerability. If no patch is available, disable the ZeroTier VPN feature and restrict network access to these devices via firewall rules or network segmentation.
IR315/IR305/IR615: firmware 1.0.121 | IR302: firmware 3.5.112
- 1. Identify the exact IR model number (IR302, IR305, IR315, or IR615) and current firmware version via the device web interface or CLI
- 2. Navigate to the official InHand Networks support website (www.inhand.com) and locate the firmware download section
- 3. Download the appropriate fixed firmware: IR315/IR305/IR615 to version 1.0.121, IR302 to version 3.5.112
- 4. Back up the current device configuration before upgrading
- 5. Access the device administration interface and navigate to the Firmware Upgrade or System Maintenance section
- 6. Upload the downloaded firmware file and initiate the upgrade process
- 7. Wait for the upgrade to complete and the device to reboot automatically
- 8. Verify the new firmware version is installed and confirm all device functions operate normally
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-38703 — 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-38703 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