dbcve.org
InstrumentstudioApplication · Ni

CVE-2026-9142

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 2.18.0 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
There is an insecure default credentials vulnerability in NI grpc-device when TLS configuration is not present and the server is bound beyond loopback.  This may allow an unauthenticated user access to the server on the local network.  This affects NI grpc-device 2.17.0 and prior versions.

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

NI grpc-device server versions 2.17.0 and prior contain insecure default credentials that are exposed when TLS configuration is omitted and the server binds to a network-accessible interface (non-loopback). Attackers on the local network can authenticate without credentials, achieving unauthenticated access to the gRPC device server.

MitigationEnable TLS configuration and proper authentication mechanisms on the grpc-device server; if network access is unnecessary, bind exclusively to loopback interface; otherwise update to a patched version when available.

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
InstrumentstudioApplication
Affected:<= 2025= 2026
Ni Grpc Device ServerApplication
Affected:< 2.18.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 grpc-device server installation
    Locate the grpc-device server executable or service on the system (commonly found in NI installation directories such as C:\Program Files\National Instruments\ or /usr/local/ni/). Check for grpc-device-server.exe or ni_grpc_device_server service.
    Affected if The grpc-device server software is installed on the system.
  2. Determine installed grpc-device server version
    Run the grpc-device server with a version flag (such as --version) or inspect the server binary properties/details. Compare the version number against the affected range: versions 2.17.0 and prior, or InstrumentStudio versions 2025 and 2026.
    Affected if The installed version is 2.17.0 or earlier, or InstrumentStudio 2025/2026 is in use.
  3. Inspect TLS configuration status
    Examine the grpc-device server configuration file or startup parameters for TLS settings. Look for flags such as --tls, --use_ssl, or similar TLS-enabling options. Check whether SSL/TLS certificates are configured.
    Affected if TLS configuration is omitted or disabled on the server.
  4. Verify server binding interface
    Review the server configuration or runtime logs to determine which network interface the server is bound to. Look for binding to 0.0.0.0 (all interfaces), the machine hostname IP, or any non-loopback address, versus 127.0.0.1 (loopback only).
    Affected if The server binds to a network-accessible interface (non-loopback address).
  5. Confirm network accessibility
    Check if the server is listening on a non-loopback IP address by running network status commands (such as netstat -an) and looking for the grpc-device server port (typically port 3581) bound to an external IP.
    Affected if The server listens on an IP address other than 127.0.0.1.

The environment is affected if grpc-device server version 2.17.0 or earlier (or InstrumentStudio 2025/2026) is running with TLS disabled and bound to a non-loopback interface, allowing unauthenticated network access.

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 2.18.0 or later
Fixed in 2.18.0
Interim mitigation

Enable TLS configuration and proper authentication mechanisms on the grpc-device server; if network access is unnecessary, bind exclusively to loopback interface; otherwise update to a patched version when available.

Recommended fix High confidence

NI grpc-device server version 2.18.0 or later

  1. 1. Identify the currently installed NI grpc-device server version by checking the application or service details
  2. 2. Download NI grpc-device server version 2.18.0 or later from the official NI website (www.ni.com) or official NI distribution channels
  3. 3. Back up any existing configuration files for the NI grpc-device server
  4. 4. Uninstall or stop the current NI grpc-device server instance
  5. 5. Install the updated NI grpc-device server version 2.18.0 or later
  6. 6. Restore the backed-up configuration files to the new installation
  7. 7. Start the NI grpc-device server and verify it is running correctly
  8. 8. Confirm TLS configuration is properly enabled for production deployments (this vulnerability only manifests when TLS is not configured and server is bound beyond loopback)
Caveat Review release notes for version 2.18.0 to check for any API or configuration changes that may affect existing integrations

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

Fix this in Instrumentstudio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,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 $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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