CVE-2025-64467
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 out of bounds read vulnerability in NI LabVIEW in LVResFile::FindRsrcListEntry() when parsing a corrupted VI file. This vulnerability 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 Q3 (25.3) 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 · high confidenceAn out-of-bounds read vulnerability exists in NI LabVIEW's LVResFile::FindRsrcListEntry() function when parsing corrupted VI files. The function fails to properly validate buffer boundaries while processing resource list entries, allowing memory reads outside allocated buffers. This can leak sensitive memory contents or potentially enable arbitrary code execution when a user opens a specially crafted malicious VI file.
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= 2022= 2023= 2024= 2025CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 LabVIEW versionCheck the LabVIEW installation via Windows Add/Remove Programs, or open LabVIEW and navigate to Help > About NI LabVIEW. The version number is displayed there.Affected if The installed version is 2022, 2023, 2024, or 2025.
-
Locate LabVIEW executable to confirm installationSearch for LabVIEW executables in typical installation directories such as C:\Program Files\National Instruments\LabVIEW [version]\ or verify via the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW.Affected if LabVIEW executables are found and version matches affected range.
-
Determine if VI file handling is activeCheck if the system or user workflow involves opening .vi files, particularly from external sources, network shares, or email attachments. Examine file association settings for .vi files pointing to installed LabVIEW versions.Affected if Users routinely open VI files from untrusted or external sources using the affected LabVIEW installation.
-
Check for suspicious VI file processingReview any available application logs, endpoint detection logs, or sandbox reports for evidence of LabVIEW processing unusual or corrupted VI files. Monitor for file access events on .vi files.Affected if Evidence exists of LabVIEW opening malformed or untrusted VI files.
A system is affected if NI LabVIEW version 2022, 2023, 2024, or 2025 is installed and users can open potentially untrusted or malicious VI files with that installation.
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.
From vendor dataDo not open VI files from untrusted or unverified sources. Apply vendor patches when released and consider deploying endpoint detection or application sandboxing to intercept suspicious file operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64467 — 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-2025-64467 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