CVE-2025-64468
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 a use-after-free vulnerability in sentry!sentry_span_set_data() 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 · moderate confidenceA use-after-free vulnerability exists in sentry_span_set_data() when parsing corrupted VI (LabVIEW) files. The vulnerability occurs because memory is accessed after being freed during the parsing process, potentially allowing an attacker to achieve information disclosure or arbitrary code execution by tricking a user into opening a specially crafted 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 versionOpen LabVIEW and go to Help > About LabVIEW, or check the installation directory folder name (typically C:\Program Files\National Instruments\LabVIEW 20XX)Affected if Version is 2022, 2023, 2024, or 2025 (any subversion within these release years)
-
Confirm LabVIEW is used to open VI filesCheck for recent .vi file access - examine Windows recent files, LabVIEW's recent files list (File > Recent Files), or check the application event log for VI file operationsAffected if LabVIEW is actively used to open .vi files from any source
-
Assess VI file source trust postureReview whether VI files opened in LabVIEW originate from untrusted or unknown sources, including downloads, email attachments, or external mediaAffected if Users open VI files from untrusted or unknown origins without verification
You are affected if you have LabVIEW 2022-2025 installed AND routinely open VI files, particularly from untrusted sources, since the vulnerability triggers during VI file parsing.
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 · scopedUsers should avoid opening VI files from untrusted sources. Organizations should deploy the affected NI LabVIEW 2025 Q3 (25.3) and prior versions in restricted environments and monitor for vendor patches addressing this memory corruption issue.
LabVIEW version newer than 2025 Q3 (25.3) - contact NI for specific patch version
- Check NI's official security advisories or LabVIEW download page for the latest patched version
- If a newer version than 25.3 is available, download and install it from www.ni.com
- Ensure all LabVIEW instances are closed before installing the update
- After installation, verify the version number matches the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64468 — 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-64468 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