dbcve.org
Ir915l Fq39 S FirmwareOperating system · Inhandnetworks

CVE-2026-38716

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 Python application export function. This 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 · high confidence

Command injection vulnerability in the Python application export function of InHand Networks IR912 and IR915 routers (V1.0.0.r20042 and earlier) allows remote attackers to execute arbitrary commands as root due to insufficient input sanitization in the export functionality.

MitigationApply vendor patches when available; if no patch exists, restrict network access to the device management interface, implement network segmentation, and disable unnecessary export features until remediation is possible.

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 device model and firmware version
    Access the device web management interface or use SNMP/telnet/ssh to retrieve the firmware version information. Look for version display in system information or status pages.
    Affected if The firmware version is InHand Networks IR915l Fq39 S or IR912l Fq58 and is earlier than 1.0.0.r20044 (for example, 1.0.0.r20042 or older)
  2. Verify the Python export application is present
    Check the device filesystem for the Python application that handles export functionality. This may be located in directories such as /usr/bin/, /www/, or application-specific paths accessible via the device management interface.
    Affected if The Python export application binary or script exists on the device and the firmware version is in the affected range
  3. Confirm export functionality is accessible
    Locate the export function endpoint in the web interface or API. The vulnerability exists in the export function, so this feature must be exposed for exploitation. Check for export-related URLs, forms, or API calls.
    Affected if The export feature is enabled and accessible through the device management interface, and the firmware version is vulnerable

The device is affected if it is an IR912 or IR915 router running firmware version earlier than 1.0.0.r20044 and the Python export functionality is exposed via the management interface.

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

Apply vendor patches when available; if no patch exists, restrict network access to the device management interface, implement network segmentation, and disable unnecessary export features until remediation is possible.

Recommended fix High confidence

1.0.0.r20044 or later

  1. Identify the exact model number (IR912 or IR915) and current firmware version of the InHand Networks device
  2. Navigate to InHand Networks official support website (www.inhand.com) and locate the firmware download section for your device model
  3. Download firmware version 1.0.0.r20044 or later for your specific device model (IR912l Fq58 or Ir915l Fq39 S)
  4. Review InHand Networks firmware upgrade documentation for proper upgrade procedure
  5. Back up current device configuration if possible
  6. Upload and apply the new firmware version following the manufacturer's recommended upgrade process
  7. After upgrade, verify the device is operational and the firmware version shows 1.0.0.r20044 or later
  8. Validate that the command injection vulnerability is no longer present by confirming the export function properly sanitizes input
Caveat Firmware upgrades carry inherent risks; test in a non-production environment first if possible, and ensure stable power during the upgrade process

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
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,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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