Menu

Star on GitHub · 3.2k

CVE-2026-64203

7.8 · HIGH

There is a memory corruption vulnerability recently discovered in NI LabVIEW that may result in information disclosure or arbitrary code execution.

Published Aug 25, 2026CWE-125EPSS 0.19%

Overview

CVE-2026-64203 is a high-severity vulnerability. It was published on August 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

There is a memory corruption vulnerability recently

discovered in NI LabVIEW that 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 2026 Q3 (26.3.0) and prior versions.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64203?

CVE-2026-64203 is a high-severity vulnerability. It was published on August 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64203?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-64203?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64203?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64203 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all