NI grpc-device/InstrumentStudio up to 2.17.0 size numeric conversion

Summaryinfo

A vulnerability was found in NI grpc-device and InstrumentStudio up to 2.17.0. It has been rated as problematic. This issue affects some unknown processing. The manipulation of the argument size leads to numeric conversion. This vulnerability is referenced as CVE-2026-9143. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in NI grpc-device and InstrumentStudio up to 2.17.0. It has been rated as problematic. This issue affects an unknown function. The manipulation of the argument size with an unknown input leads to a numeric conversion vulnerability. Using CWE to declare the problem leads to CWE-681. When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur. Impacted is integrity. The summary by CVE is:

There is an incorrect conversion between numeric types vulnerability in NI grpc-device due to missing range checks in CodeGen.  This may silently discard high bits if a size value exceeded the target type's range. This affects NI grpc-device 2.17.0 and prior versions.

The weakness was published by Sebastián Alba Vives. The advisory is shared at ni.com. The identification of this vulnerability is CVE-2026-9143 since 05/20/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/19/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-38032). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• NI

Name

• grpc-device
• InstrumentStudio

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion