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.
CVE-2026-64202
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026Memory Corruption Vulnerabilities in NI LabVIEW - NI
https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/memory-corruption-vulnerabilities-ni-labview.htmlVendor Advisories for CVE-2026-64202(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:19 UTCGHSA enrichment
- 2026-08-29 09:52 UTCEG score recompute
- 2026-08-29 09:52 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 21:24 UTCGHSA enrichment
- 2026-08-28 19:24 UTCGHSA enrichment
- 2026-08-28 06:39 UTCGHSA enrichment
- 2026-08-27 18:11 UTCEG score recompute
- 2026-08-27 18:11 UTCGHSA enrichment
- 2026-08-27 04:30 UTCGHSA enrichment
- 2026-08-26 15:59 UTCEG score recompute
- 2026-08-26 15:59 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 04:10 UTCEG score recompute
- 2026-08-26 04:10 UTCGHSA enrichment
- 2026-08-25 18:28 UTCEG score recompute
- 2026-08-25 17:55 UTCEG score recompute
- 2026-08-25 17:25 UTCEG score recompute
- 2026-08-25 17:00 UTCEG score recompute
- 2026-08-25 17:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-64202?
When was CVE-2026-64202 disclosed?
Is CVE-2026-64202 actively exploited?
What is the CVSS score of CVE-2026-64202?
How do I remediate CVE-2026-64202?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64202
Is Your Infrastructure Affected by CVE-2026-64202?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.