NI LabVIEW up to 22.3.6/23.3.7/24.3.4/25.3.2 VI File Parser sentry_span_set_data use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in NI LabVIEW up to 22.3.6/23.3.7/24.3.4/25.3.2. Impacted is the function sentry_span_set_data of the component VI File Parser. The manipulation results in use after free.
This vulnerability is identified as CVE-2025-64468. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability, which was classified as critical, was found in NI LabVIEW up to 22.3.6/23.3.7/24.3.4/25.3.2. Affected is the function sentry_span_set_data of the component VI File Parser. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
There 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
The weakness was released by Michael Heinzl. The advisory is available at ni.com. This vulnerability is traded as CVE-2025-64468 since 11/04/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 12/18/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 22.3.0
- 22.3.1
- 22.3.2
- 22.3.3
- 22.3.4
- 22.3.5
- 22.3.6
- 23.3.0
- 23.3.1
- 23.3.2
- 23.3.3
- 23.3.4
- 23.3.5
- 23.3.6
- 23.3.7
- 24.3.0
- 24.3.1
- 24.3.2
- 24.3.3
- 24.3.4
- 25.3.0
- 25.3.1
- 25.3.2
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/04/2025 CVE reserved12/18/2025 Advisory disclosed
12/18/2025 VulDB entry created
12/18/2025 VulDB entry last update
Sources
Advisory: ni.comResearcher: Michael Heinzl
Status: Confirmed
CVE: CVE-2025-64468 (🔒)
GCVE (CVE): GCVE-0-2025-64468
GCVE (VulDB): GCVE-100-337386
Entry
Created: 12/18/2025 17:20Changes: 12/18/2025 17:20 (75)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.