{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-16233 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-16233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-16233 is a high-severity memory corruption vulnerability in NI LabVIEW, published on 25 Aug 2026. 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-2026-16233 and fix it if it is affected.\n\nWhat it is: CVE-2026-16233 is a high-severity memory corruption vulnerability in NI LabVIEW, published on 25 Aug 2026. 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-2026-16233 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-2026-16233/ (Markdown: https://insights.sbomify.com/CVE-2026-16233/index.md)","id":"CVE-2026-16233","markdown":"https://insights.sbomify.com/CVE-2026-16233/index.md","name":"CVE-2026-16233","record":{"aliases":["GHSA-p3x9-7mrv-5rx5"],"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 file in 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":"There is a memory corruption vulnerability recently\ndiscovered in NI LabVIEW that may result in information disclosure or arbitrary\ncode execution.  Successful exploitation requires an attacker to get a\nuser to open a specially crafted VI.  This vulnerability affects NI\nLabVIEW 2026 Q3 (26.3.0) 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 when loading VI","id":"CVE-2026-16233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-16234"},"packages":[],"prev":{"headline":"Check Point SmartConsole Improper Authentication","id":"CVE-2026-16232"},"products":["LabVIEW"],"published":"2026-08-25","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 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":"2026-08-26","vendors":["NI"]},"summary":"An attacker can achieve arbitrary code execution or information disclosure by tricking a user into opening a specially crafted VI file in LabVIEW.","url":"https://insights.sbomify.com/CVE-2026-16233/"}