PatchSiren cyber security CVE debrief
CVE-2025-64461 National Instruments CVE debrief
National Instruments LabVIEW contains an out-of-bounds write vulnerability that can be triggered when a user opens a specially crafted VI (Virtual Instrument) file. This memory corruption flaw may allow an attacker to execute arbitrary code with the privileges of the user running LabVIEW. The attack requires local access in the sense that the attacker must convince a user to open a malicious file, but does not require elevated privileges or complex interaction. The vulnerability affects multiple supported versions of LabVIEW from 2022 through 2025, with LabVIEW 2021 noted as no longer in mainstream support. National Instruments has released patched versions for all supported releases.
- Vendor
- National Instruments
- Product
- LabVIEW
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2025-12-18
- Original CVE updated
- 2025-12-18
- Advisory published
- 2025-12-18
- Advisory updated
- 2025-12-18
Who should care
Organizations using National Instruments LabVIEW in engineering, test, measurement, and industrial control applications, particularly those in operational technology (OT) environments where LabVIEW is deployed for data acquisition and control systems. Security teams responsible for software supply chain and file-based attack vectors should prioritize patching.
Technical summary
Out-of-bounds write in LabVIEW VI file parsing
Defensive priority
HIGH
Recommended defensive actions
- Upgrade to vendor-provided patched versions: LabVIEW 2025 Q3 Patch 3 or later, LabVIEW 2024 Q3 Patch 5 or later, LabVIEW 2023 Q3 Patch 8 or later, or LabVIEW 2022 Q3 Patch 7 or later via NI Package Manager or Software
- Implement application whitelisting and execution controls to prevent unauthorized LabVIEW file execution
- Train users to recognize and avoid opening untrusted VI files from unknown sources
- Consider network segmentation for systems running LabVIEW in operational technology environments
- Review and apply CISA ICS recommended practices for defense-in-depth strategies
Evidence notes
CVE published 2025-12-18 per CISA CSAF advisory ICSA-25-352-03. CVSS 3.1 score 7.8 (HIGH) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Attack vector is local, requiring user interaction to open a crafted VI file.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-64461 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-64461
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-64461 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-64461
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source item URL
Unverified legacy reference
URL: https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/OT/white/2025/icsa-25-352-03.json
cisa_csaf
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/news-events/ics-advisories/icsa-25-352-03
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/ics/alerts/ICS-ALERT-10-301-01
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/resources-tools/resources/ics-recommended-practices
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/sites/default/files/publications/Cybersecurity_Best_Practices_for_Industrial_Control_Systems.pdf
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/topics/industrial-control-systems
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/sites/default/files/publications/emailscams0905.pdf
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/ncas/tips/ST04-014
Reference
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.