CVE-2026-48137
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 untrusted pointer dereference vulnerability in the NI grpc-device sideband streaming API that may allow an attacker to cause an arbitrary memory dereference, potentially resulting in remote code execution. Successful exploitation requires an attacker to supply a specially crafted Moniker protobuf message. 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 confidenceAn untrusted pointer dereference vulnerability exists in the NI grpc-device sideband streaming API that allows attackers to cause arbitrary memory dereference by sending a specially crafted Moniker protobuf message, potentially achieving remote code execution.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed NI InstrumentStudio versionCheck the Windows Programs and Features list, or look for InstrumentStudio in Program Files/National Instruments, and locate the version information in the application properties or README file.Affected if The installed version is 2025 or earlier, or exactly version 2026.
-
Identify installed NI Grpc Device Server versionLocate the grpc-device server installation directory (typically under National Instruments) and check the version file, DLL properties, or run 'grpc-device-server --version' if available from command line.Affected if The installed version is 2.17.0 or lower, or any version below 2.18.0.
-
Verify grpc-device service is running and exposedCheck Windows Services for 'NI gRPC Device Server' status, or use 'netstat -an | grep 3581' to see if the grpc-device port is listening on network interfaces.Affected if The service is running and listening on accessible network interfaces (especially external/remote IPs).
-
Confirm sideband streaming API usageReview grpc-device configuration files (typically in the installation directory or under C:\ProgramData\National Instruments\) for sideband streaming settings, and check if any client applications use the Moniker protobuf message type.Affected if Sideband streaming is enabled in configuration and clients are actively sending Moniker protobuf messages to the service.
A user is affected if they have NI InstrumentStudio 2025 or earlier/2026, or NI Grpc Device Server version below 2.18.0, and the grpc-device service with sideband streaming is exposed on the network.
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
Update NI grpc-device to a version beyond 2.17.0 when a patch is available. Until then, restrict network access to the grpc-device service and monitor for suspicious protobuf traffic.
Ni Grpc Device Server 2.18.0 or later
- Obtain NI Grpc Device Server version 2.18.0 or later from NI's official distribution channels (NI website or GitHub repository)
- Stop the running NI Grpc Device Server service
- Backup the current NI Grpc Device Server installation directory and configuration files
- Install version 2.18.0 or later of NI Grpc Device Server
- Start the NI Grpc Device Server service
- Verify the installed version is 2.18.0 or later using the server's version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48137 — 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-48137 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