dbcve.org
Ir315 FirmwareOperating system · Inhandnetworks

CVE-2026-38707

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 1.0.121 / 3.5.112 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 command injection vulnerability exists in the IPSec 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 confidence

A command injection vulnerability exists in the IPSec VPN feature of InHand Networks IR302, IR305, IR315, and IR615 routers. The flaw allows remote attackers to inject arbitrary commands through the VPN configuration interface, which are then executed with ROOT privileges on the affected device.

MitigationApply the vendor-supplied firmware update to a patched version that addresses this command injection vulnerability. If no patch is available, consider network segmentation to limit exposure of the IPSec VPN interface to untrusted networks.

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
Ir315 FirmwareOperating system
Affected:< 1.0.121
Ir302 FirmwareOperating system
Affected:< 3.5.112
Ir615 FirmwareOperating system
Affected:< 1.0.121
Ir305 FirmwareOperating system
Affected:< 1.0.121

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
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 checks

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

  1. Identify device model and firmware version
    Access the device web interface or CLI and locate the system information or firmware version display. This is typically found under Status, System, or About sections in the web UI, or via 'show version' or 'system info' commands in CLI.
    Affected if The device is an IR302, IR305, IR315, or IR615 with firmware version below 3.5.112 (IR302) or below 1.0.121 (IR305/IR315/IR615)
  2. Confirm IPSec VPN feature is configured
    Check the VPN settings in the device web interface under VPN or IPSec configuration sections. Look for active IPSec tunnels, policies, or profiles.
    Affected if IPSec VPN is enabled and configured on the device - the vulnerability is exploited through the VPN configuration interface
  3. Verify management access exposure
    Review network access settings for the VPN management interface. Check if the VPN configuration page is accessible from untrusted networks or if unauthenticated access is permitted.
    Affected if The VPN management interface is exposed to untrusted networks or allows unauthenticated access
  4. Inspect for signs of remote compromise
    Review system logs for unexpected commands, new user accounts, or unusual network connections. Check for unfamiliar processes or binaries in /usr/bin, /bin, or /sbin directories.
    Affected if Logs show unexpected command executions, unfamiliar binaries, or suspicious outbound connections to unknown IP addresses

You are affected if you have an IR302 (firmware < 3.5.112) or IR305/IR315/IR615 (firmware < 1.0.121) with IPSec VPN feature enabled and the management interface is exposed to untrusted networks.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.121 / 3.5.112 or later
Fixed in 1.0.1213.5.112
Interim mitigation

Apply the vendor-supplied firmware update to a patched version that addresses this command injection vulnerability. If no patch is available, consider network segmentation to limit exposure of the IPSec VPN interface to untrusted networks.

Recommended fix High confidence

IR302: firmware >= 3.5.112 | IR305: firmware >= 1.0.121 | IR315: firmware >= 1.0.121 | IR615: firmware >= 1.0.121

  1. 1. Identify the exact InHand Networks IR device model (IR302, IR305, IR315, or IR615) requiring remediation
  2. 2. Visit InHand Networks official support website (www.inhand.com) or contact InHand Networks directly to obtain the firmware upgrade file
  3. 3. Download the appropriate fixed firmware version: IR302 upgrade to version 3.5.112 or later, IR305 upgrade to version 1.0.121 or later, IR315 upgrade to version 1.0.121 or later, IR615 upgrade to version 1.0.121 or later
  4. 4. Review the InHand Networks firmware upgrade documentation for proper installation procedures
  5. 5. Back up the current device configuration before performing the upgrade
  6. 6. Upload and apply the new firmware through the device's web management interface or CLI, following vendor instructions
  7. 7. After upgrade, verify the device is functioning correctly and confirm the firmware version has been updated
Caveat Review InHand Networks release notes for any configuration or feature changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ir315 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-38707 — 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-38707 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