CVE-2025-64468

Published: Dec 18, 2025Modified: Jun 17, 2026

8.5

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XShow less

Source: security@ni.com (Secondary)

Description

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

Affected (31)

Products: Ni: Labview

1 product

Labview

Configuration A

31 vulnerable

Vulnerable Software	Affected Versions
Ni Labview	Version 2022 q1
Ni Labview	Version 2022 q3
Ni Labview	Version 2022 q3_patch1
Ni Labview	Version 2022 q3_patch2
Ni Labview	Version 2022 q3_patch4
Ni Labview	Version 2022 q3_patch5
Ni Labview	Version 2022 q3_patch6
Ni Labview	Version 2023 q1
Ni Labview	Version 2023 q3
Ni Labview	Version 2023 q3_patch1
Ni Labview	Version 2023 q3_patch2
Ni Labview	Version 2023 q3_patch3
Ni Labview	Version 2023 q3_patch4
Ni Labview	Version 2023 q3_patch5
Ni Labview	Version 2023 q3_patch6
Ni Labview	Version 2023 q3_patch7
Ni Labview	Version 2024
Ni Labview	Version 2024 q1
Ni Labview	Version 2024 q1_patch1
Ni Labview	Version 2024 q3
Ni Labview	Version 2024 q3_patch1
Ni Labview	Version 2024 q3_patch2
Ni Labview	Version 2024 q3_patch3
Ni Labview	Version 2024 q3_patch4
Ni Labview	Version 2025 q1
Ni Labview	Version 2025 q1_patch1
Ni Labview	Version 2025 q1_patch2
Ni Labview	Version 2025 q1_patch3
Ni Labview	Version 2025 q3
Ni Labview	Version 2025 q3_patch1
Ni Labview	Version 2025 q3_patch2

Related CWEs

CWE-416

Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

References (1)

https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/multiple-memory-corruption-vulnerabilities-in-ni-labview.html

Source: security@ni.com

MitigationVendor Advisory

Timeline

No history available yet.