What is CVE-2026-18445?

CVE-2026-18445 is Integer Overflow Vulnerability Resulting in an Out of Bounds Write in NI LabVIEW. The supplied enrichment data classifies it as Memory Corruption mapped to CWE-190 Integer Overflow or Wraparound.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-18445. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-18445 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-18445. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-18445 using CVSS 6.6, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumMemory Corruption

CVE-2026-18445

CVE-2026-18445 — Integer Overflow Vulnerability Resulting in an Out of Bounds Write in NI LabVIEW

There is an integer overflow vulnerability resulting in an out-of-bounds write recently discovered in NI LabVIEW. This may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially crafted VI file. This vulnerability affects NI LabVIEW 2026 Q3 and prior versions.

Published Aug 25, 2026Updated Aug 25, 2026Sources: NVD, NI (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

5 products listed

CVSS base

6.6

medium · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade LabVIEW to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
NI	LabVIEW	0 to < 23.0.0	Vulnerable
NI	LabVIEW	23.1.0 to < 23.3.10	Vulnerable
NI	LabVIEW	24.1.0 to < 24.3.7	Vulnerable
NI	LabVIEW	25.1.0 to < 25.3.5	Vulnerable
NI	LabVIEW	26.1.0 to < 26.3.1	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

Low

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

None

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.6	CVSS 3.1	medium	1.8	4.7	ni.com (CNA), NI (CNA), GHSA
6.9	CVSS 4.0	medium	—	—	NI (CNA)

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-190 · Integer Overflow or Wraparound

DoS: Crash, Exit, or Restart
DoS: Resource Consumption (CPU)
DoS: Resource Consumption (Memory)
DoS: Instability

Mitigation: Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.

Weakness & attack patterns

CWE-190Integer Overflow or Wraparound

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-92 · Forced Integer Overflow

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.6 (AV:L)
Aug 25, 2026 · NVD
Initial · CVE published
Aug 25, 2026 · NVD
Added · GHSA-wh6m-8vv3-wpp9 published (medium)
Aug 25, 2026 · GitHub Security Advisory

Source activity

Readings a source repeats on a schedule, counted rather than listed.

1×CVE modified by NIST, Modified, LinkAug 25, 2026 · SOCRadar CTI

References

3 on the record

www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/integer-overflow-vulnerability-resulting-in-an-out-of-bounds-write-in-ni-labview.html
Vendor Advisory, NIST
nvd.nist.gov/vuln/detail/CVE-2026-18445
NVD
github.com/advisories/GHSA-wh6m-8vv3-wpp9
Exploit, Third Party Advisory

Elsewhere on this site

NIevery CVE for this vendor
Memory Corruptionsame class
CWE-190other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-18445 is Integer Overflow Vulnerability Resulting in an Out of Bounds Write in NI LabVIEW, a medium vulnerability affecting LabVIEW from NI. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-18445. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-18445. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.6 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.