CVE-2026-9143
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 · uneditedThere 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.
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 confidenceA numeric type conversion vulnerability exists in NI grpc-device's CodeGen component where missing range checks allow silent discarding of high bits when size values exceed the target type's range. This data integrity issue can cause unexpected behavior due to truncated values during code generation.
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<= 2025= 2026< 2.18.0CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check NI InstrumentStudio versionOpen NI InstrumentStudio and navigate to Help > About, or check the installed programs list in Windows Control Panel to locate the version numberAffected if The version is 2025 or earlier, or exactly version 2026
-
Check NI gRPC Device Server versionRun 'grpc-device-server --version' from command line, or check the installed gRPC Device Server version in NI MAX or program files directoryAffected if The version is below 2.18.0
-
Verify CodeGen component usageInspect your project configuration or build scripts to determine if the CodeGen component is being invoked for code generation tasksAffected if CodeGen is actively used for generating code from .proto files or similar definitions
You are affected if you have an affected InstrumentStudio version (2025 or earlier, or 2026) or gRPC Device Server version below 2.18.0 AND you actively use the CodeGen component for code generation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.18.0
Add proper range validation in CodeGen before numeric type conversions to ensure values fit within target type bounds; upgrade to any version beyond 2.17.0 that includes the fix.
NI Grpc Device Server 2.18.0 or later
- 1. Identify the currently installed version of NI Grpc Device Server by checking the application or service version
- 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. Back up any existing configuration files and data for the NI Grpc Device Server
- 4. Stop the NI Grpc Device Server service if it is currently running
- 5. Install version 2.18.0 or the latest available version that addresses the vulnerability
- 6. Restore any necessary configuration files from the backup
- 7. Start the NI Grpc Device Server service
- 8. Verify the service is running correctly and test that grpc-device functionality operates as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9143 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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