dbcve.org
Ir315 FirmwareOperating system · Inhandnetworks

CVE-2026-38702

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 Admin Access 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 Admin Access feature of InHand Networks IR302, IR305, IR315, and IR615 firmware. Attackers can inject arbitrary commands through the Admin Access interface, achieving ROOT privilege escalation on affected devices.

MitigationApply vendor firmware updates when available; if no patch exists, consider network segmentation and disabling Admin Access from untrusted networks as interim controls. Restrict administrative interfaces to trusted networks only.

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 your InHand Networks device model
    Check the device label, web interface header, or CLI output for the exact model (IR302, IR305, IR315, or IR615). This is required because version thresholds differ by model.
    Affected if The device is one of the four affected models (IR302, IR305, IR315, IR615).
  2. Determine the installed firmware version
    Log into the device web interface and navigate to System > Status, or use CLI (SSH/Telnet) and run 'version' or 'show version' to obtain the firmware build number.
    Affected if The firmware version is lower than the threshold for your model: IR315 < 1.0.121, IR302 < 3.5.112, IR615 < 1.0.121, or IR305 < 1.0.121.
  3. Verify Admin Access feature status
    In the web interface, go to System > Admin Access or Security > Admin Access to confirm whether this feature is enabled. If using CLI, check for admin access configuration commands.
    Affected if Admin Access is enabled on the device.
  4. Check network exposure of Admin Access
    Review firewall rules, ACLs, or network segmentation to determine if the Admin Access interface (typically HTTP/HTTPS on ports 80/443 or management ports) is reachable from untrusted networks or the internet.
    Affected if Admin Access is exposed to untrusted networks or the internet without proper access controls.

You are affected if your device is an IR302, IR305, IR315, or IR615 running firmware below the specified version threshold AND Admin Access is enabled and reachable from an untrusted network.

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 vendor firmware updates when available; if no patch exists, consider network segmentation and disabling Admin Access from untrusted networks as interim controls. Restrict administrative interfaces to trusted networks only.

Recommended fix High confidence

Ir315: >=1.0.121 | Ir302: >=3.5.112 | Ir615: >=1.0.121 | Ir305: >=1.0.121

  1. 1. Identify the exact InHand Networks IR device model (IR302, IR305, IR315, or IR615) in your environment
  2. 2. Determine the current firmware version by accessing the device's web interface or using the CLI command `show version`
  3. 3. Download the appropriate firmware update from the official InHand Networks website (www.inhand.com) or authorized support portal
  4. 4. For each affected device, access the Admin Access section in the web management interface
  5. 5. Navigate to the Firmware Upgrade or System Maintenance section
  6. 6. Upload the new firmware file (version 1.0.121 or later for IR305/IR315/IR615; version 3.5.112 or later for IR302)
  7. 7. Wait for the upload to complete and the device to reboot automatically
  8. 8. After reboot, verify the new firmware version is installed by checking `show version`
Caveat Firmware upgrades may temporarily interrupt connectivity; ensure backup of configuration before upgrading; verify compatibility with dependent systems after upgrade

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

Fix this in Ir315 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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