dbcve.org
Ir915l Fq39 S FirmwareOperating system · Inhandnetworks

CVE-2026-38717

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-18
Fix available
A fix is available. Upgrade to 1.0.0.r20044 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
InHand Networks IR912 V1.0.0.r20042 and IR915 V1.0.0.r20042 (including earlier versions) were discovered to contain a command injection vulnerability in the file upload function. The vulnerability allows remote attackers to execute arbitrary commands as root via a crafted input.

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 confidence

InHand Networks IR912 and IR915 routers (V1.0.0.r20042 and earlier) contain a command injection vulnerability in the file upload function that allows remote attackers to execute arbitrary commands with root privileges.

MitigationRestrict network access to the device's management interface, disable or limit the file upload function if possible, and apply any available firmware updates from InHand 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
Ir915l Fq39 S FirmwareOperating system
Affected:< 1.0.0.r20044
Ir912l Fq58 FirmwareOperating system
Affected:< 1.0.0.r20044

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 the router model
    Check the device label, web management interface (typically at /dev_info.asp or similar), or CLI output (show version or system info command) to confirm the device is an InHand Networks IR912 or IR915 series router.
    Affected if The device model is IR912L FQ58 or IR915L FQ39 S.
  2. Check the installed firmware version
    Log into the router web interface or CLI and navigate to the firmware/version information page. Common paths include the status page, system info, or running 'version' command via CLI.
    Affected if The firmware version is older than 1.0.0.r20044.
  3. Verify file upload functionality access
    Check if the web-based file upload or firmware upgrade feature is accessible. Look for upload/upgrade pages in the web interface (commonly under Administration, Maintenance, or System Tools sections).
    Affected if The file upload or firmware upgrade interface is exposed and accessible.
  4. Confirm management interface exposure
    Determine if the router web management interface is reachable from untrusted networks by checking firewall rules, ACLs, or network segmentation configurations.
    Affected if The router management interface (HTTP/HTTPS) is accessible from external or untrusted networks.

The environment is affected if the device is an IR912L FQ58 or IR915L FQ39 S router running firmware version 1.0.0.r20044 or earlier, and the file upload function is accessible.

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.0.r20044 or later
Fixed in 1.0.0.r20044
Interim mitigation

Restrict network access to the device's management interface, disable or limit the file upload function if possible, and apply any available firmware updates from InHand Networks.

Recommended fix High confidence

1.0.0.r20044

  1. Locate the InHand Networks IR912/IR915 firmware download page on InHand's official website (www.inhand.com)
  2. Download firmware version 1.0.0.r20044 or later for your specific device model (IR912l Fq58 or IR915l Fq39 S)
  3. Access the device's web management interface using administrator credentials
  4. Navigate to the firmware upgrade or system maintenance section
  5. Upload and apply the new firmware version 1.0.0.r20044
  6. After the upgrade completes, verify the firmware version in the device interface to confirm the patch was applied

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

Fix this in Ir915l Fq39 S Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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