Quick answers
- Is CVE-2026-32863 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32863 being exploited in the wild.
- How severe is CVE-2026-32863?
- High severity, with a CVSS score of 7.8, published 7 April 2026.
- Which products and versions are affected?
- NI Labview 2026 Q1 (26.1.0) and prior versions.
- Is there a fix for CVE-2026-32863?
- A patch was published on 2026-04-07. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32863 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-32863?
- Check whether you run NI Labview at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A memory corruption vulnerability exists in NI LabVIEW due to an out-of-bounds read within the 'sentry_transaction_context_set_operation()' function. The flaw is triggered when the application processes a specially crafted Virtual Instrument (.VI) file. This is a local attack vector requiring user interaction (opening the file). Successful exploitation can lead to arbitrary code execution or information disclosure by reading beyond allocated memory buffers. The vulnerability affects versions up to and including LabVIEW 2026 Q1 (26.1.0). NI has released patches for various versions, including LabVIEW 2026 Q1 Patch 1.
Affected products
- NI LabVIEW 2026 Q1 (26.1.0) and prior versions
Timeline
- 2026-04-07: disclosed
- 2026-04-07: advisory
- 2026-04-07: patched