CVE-2026-32864
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere is a memory corruption vulnerability due to an out-of-bounds read in mgcore_SH_25_3!aligned_free() in NI LabVIEW. 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 file. This vulnerability affects NI LabVIEW 2026 Q1 (26.1.0) and prior versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an out-of-bounds memory read vulnerability in the aligned_free() function within NI LabVIEW's mgcore_SH_25_3 library. The vulnerability is triggered when a user opens a specially crafted malicious VI file, potentially allowing attackers to read sensitive memory contents or achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2022= 2023= 2024= 2025= 2026CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed LabVIEW versionOpen LabVIEW and go to Help > About LabVIEW, or check the installation directory for version information in the executable propertiesAffected if The version is 2022 or older, or exactly 2023, 2024, 2025, or 2026 (any of the listed affected versions)
-
Locate the vulnerable mgcore_SH_25_3 DLLSearch for mgcore_SH_25_3.dll in the LabVIEW installation directory (commonly in the labview\bin or labview\resource directories)Affected if The DLL exists in the LabVIEW installation folder, indicating the vulnerable component is present
-
Verify the aligned_free function existsUse a tool like dumpbin or strings to inspect the DLL and confirm the presence of the aligned_free symbolAffected if The aligned_free function is found within mgcore_SH_25_3.dll, confirming the vulnerable code path exists
-
Assess VI file handling exposureReview recent VI file opens or examine the LabVIEW environment for untrusted or unknown VI files that may have been openedAffected if Untrusted or unverified VI files have been opened in the LabVIEW environment, as the vulnerability is triggered through malicious VI file parsing
A user is affected if their LabVIEW version matches 2022 or older, 2023, 2024, 2025, or 2026 AND they have the mgcore_SH_25_3 component present AND they may have opened untrusted VI files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataOrganizations should exercise caution with VI files from untrusted sources and implement file validation policies until NI releases an official patch. Users should avoid opening VI files from unknown or untrusted origins.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32864 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data