{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2631 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2631 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2631 is a high-severity memory corruption vulnerability in NI LabVIEW, published on 9 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-2631 and fix it if it is affected.\n\nWhat it is: CVE-2025-2631 is a high-severity memory corruption vulnerability in NI LabVIEW, published on 9 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-2631 in the wild and no public exploit code.\n\nAffected product: NI LabVIEW. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-2631/ (Markdown: https://insights.sbomify.com/CVE-2025-2631/index.md)","id":"CVE-2025-2631","markdown":"https://insights.sbomify.com/CVE-2025-2631/index.md","name":"CVE-2025-2631","record":{"aliases":["GHSA-grxg-r84x-j5gq"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LabVIEW engineering software","requires_auth":"none","summary":"An attacker can achieve arbitrary code execution or information disclosure by tricking a user into opening a specially crafted VI in NI LabVIEW.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NI","cpe":[{"product":"labview","vendor":"ni"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out of bounds write vulnerability due to improper bounds checking in NI LabVIEW in InitCPUInformation() 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 2025 Q1 and prior versions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Out of Bounds Write Vulnerability in NI LabVIEW in InitCPUInformation()","id":"CVE-2025-2631","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Out of Bounds Write Vulnerability in NI LabVIEW reading CPU info from cache","id":"CVE-2025-2632"},"packages":[],"prev":{"headline":"DLL Hijacking Vulnerability in NI LabVIEW","id":"CVE-2025-2630"},"products":["LabVIEW"],"published":"2025-04-09","related":[{"cvss_score":10,"headline":"Path traversal in n/a","id":"CVE-2013-5022","kev_date_added":null,"published":"2013-08-06"},{"cvss_score":8.5,"headline":"Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-16233","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-16234","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64201","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64202","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64203","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64204","kev_date_added":null,"published":"2026-08-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-09","vendors":["NI"]},"summary":"An attacker can achieve arbitrary code execution or information disclosure by tricking a user into opening a specially crafted VI in NI LabVIEW.","url":"https://insights.sbomify.com/CVE-2025-2631/"}