CVE-2026-38704
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 WireGuard 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 · high confidenceA command injection vulnerability in the WireGuard VPN feature of InHand Networks IR302, IR305, IR315, and IR615 industrial routers allows remote attackers to execute arbitrary commands with ROOT privileges due to insufficient input validation.
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 the router modelAccess the device web interface or check the device label to confirm the exact model (IR302, IR305, IR315, or IR615).Affected if The device is an IR302, IR305, IR315, or IR615 model from InHand Networks.
-
Check the installed firmware versionLog into the router administration interface and navigate to the System Status or About page to view the current firmware version. Alternatively, use the command line and run 'cat /etc/version' or check the firmware file name.Affected if The firmware version is below 3.5.112 for IR302, or below 1.0.121 for IR305, IR315, or IR615.
-
Verify if WireGuard VPN is configuredLog into the router web interface and navigate to VPN settings to check if WireGuard is enabled or any WireGuard tunnels are configured. Alternatively, check for WireGuard-related configuration files in /etc/config/ or /etc/wireguard/.Affected if WireGuard VPN is enabled or a WireGuard tunnel interface exists on the device.
-
Inspect VPN configuration for anomaliesReview the WireGuard configuration files (typically wg0.conf in /etc/config/ or /etc/wireguard/) for unexpected commands, additional interfaces, or suspicious peer entries that were not intentionally configured.Affected if The WireGuard configuration contains unexpected commands, extra interfaces, or unauthorized peer configurations that were not added by an administrator.
-
Check for signs of exploitationReview system logs in /var/log/ for any suspicious commands executed, especially those containing shell metacharacters (|, ;, $, `, or &&) in VPN-related entries. Also check for new user accounts or modified startup scripts.Affected if Logs show execution of arbitrary commands, especially with ROOT privileges, or unauthorized changes to system files indicate the device has been compromised.
You are affected if you own an IR302, IR305, IR315, or IR615 router running firmware below the specified versions AND have WireGuard VPN enabled or configured on the device.
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
Update firmware to versions newer than V3.5.108 (IR302) or V1.0.118 (IR305/IR315/IR615), or restrict network access to the VPN management interface.
IR302: firmware >= 3.5.112; IR305/IR315/IR615: firmware >= 1.0.121
- 1. Identify the exact InHand Networks IR device model (IR302, IR305, IR315, or IR615) from the affected fleet
- 2. Determine the current firmware version installed on the device via the web interface or CLI (typically via 'show version' or System > Device Info)
- 3. Navigate to the official InHand Networks support website at www.inhand.com or the InHand Networks firmware download portal
- 4. Locate and download the appropriate firmware upgrade: IR302 to version 3.5.112 or later; IR305 to version 1.0.121 or later; IR315 to version 1.0.121 or later; IR615 to version 1.0.121 or later
- 5. Review the firmware upgrade instructions in the InHand Networks product manual
- 6. Back up the current device configuration before upgrading
- 7. Upload and apply the new firmware through the device's web interface (System > Firmware Upgrade) or via TFTP/FTP if using CLI
- 8. Verify the upgrade was successful by checking the new firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38704 — 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-38704 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