CVE-2025-2634
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 · uneditedOut of bounds read vulnerability due to improper bounds checking in NI LabVIEW in fontmgr 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 Q1 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 · high confidenceAn out-of-bounds read vulnerability exists in the fontmgr component of NI LabVIEW due to improper bounds checking. An attacker can craft a malicious VI file that, when opened by a user, triggers the out-of-bounds read, potentially exposing sensitive information or enabling 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<= 2021= 2022= 2023= 2024= 2025CVSS 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 navigate to Help > About LabVIEW, or check the installation directory for version information (typically in the root LabVIEW folder name)Affected if The installed version is any of: 2021 or earlier, 2022, 2023, 2024, or 2025 (all listed versions are affected)
-
Verify fontmgr component presenceCheck the LabVIEW installation directory for the fontmgr component (typically located in the labview\resource\fonts or similar path depending on version)Affected if The fontmgr component file exists in the LabVIEW installation directory, indicating the vulnerable component is present
-
Confirm ability to open VI filesVerify that LabVIEW can open .vi files (try opening any existing VI file in the environment)Affected if LabVIEW successfully opens VI files, meaning the file parsing functionality that uses fontmgr is accessible and could process a malicious VI file
The environment is affected if LabVIEW version 2021 or earlier, 2022, 2023, 2024, or 2025 is installed, the fontmgr component exists, and the application can open VI files - all three conditions must be true for the vulnerability to be exploitable.
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.
dbcve · scopedUsers should refrain from opening VI files from untrusted sources. Organizations should update to LabVIEW versions beyond 2025 Q1 once the vendor releases a patch addressing the bounds checking in fontmgr.
LabVIEW 2025 Q2 or later
- Upgrade NI LabVIEW to a version later than 2025 Q1 (e.g., 2025 Q2 or later release)
- Do not open untrusted or specially crafted VI files in LabVIEW
- Verify the installed version after upgrade via Help > About LabVIEW
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2634 — 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-2025-2634 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