NI LabVIEW up to 22.3.6/23.3.7/24.3.4/25.3.2 FindRsrcListEntry out-of-bounds

Summaryinfo

A vulnerability has been found in NI LabVIEW up to 22.3.6/23.3.7/24.3.4/25.3.2 and classified as critical. This affects the function LVResFile::FindRsrcListEntry. Performing a manipulation results in out-of-bounds. This vulnerability is cataloged as CVE-2025-64467. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in NI LabVIEW up to 22.3.6/23.3.7/24.3.4/25.3.2. It has been classified as critical. This affects the function LVResFile::FindRsrcListEntry. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

There 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.

The weakness was shared by Michael Heinzl. The advisory is shared at ni.com. This vulnerability is uniquely identified as CVE-2025-64467 since 11/04/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around 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 the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• NI

Name

• LabVIEW

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.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion