CVE-2026-16233

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

There is a memory corruption vulnerability recently discovered in NI LabVIEW 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 2026 Q3 (26.3.0) and prior versions.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
Fix referenced — no release confirmed yet.
Web page

Memory Corruption Vulnerabilities in NI LabVIEW - NI

https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/2026/memory-corruption-vulnerabilities-ni-labview.html

Vendor Advisories for CVE-2026-16233(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 88× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 163 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-12 16:30 UTCEG score recompute
  4. 2026-10-11 20:09 UTCEG score recompute
  5. 2026-10-11 17:21 UTCEG score recompute
  6. 2026-10-11 14:54 UTCEG score recompute
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-10 11:59 UTCEG score recompute
  9. 2026-10-10 11:59 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-09 04:21 UTCEG score recompute
  12. 2026-10-09 04:21 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-08 03:14 UTCEG score recompute
  15. 2026-10-08 03:14 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-07 05:03 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-06 16:09 UTCEG score recompute
  19. 2026-10-06 16:09 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-06 02:31 UTCEG score recompute
  22. 2026-10-06 02:31 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-05 08:44 UTCEG score recompute
  25. 2026-10-05 08:44 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
Show 75 more
  1. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-04 19:49 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-04 05:15 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-03 16:26 UTCEG score recompute
  5. 2026-10-03 16:26 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-03 01:42 UTCEG score recompute
  8. 2026-10-03 01:42 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-02 12:53 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-01 22:42 UTCEG score recompute
  11. 2026-10-01 22:42 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-01 09:04 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-09-30 20:14 UTCEG score recompute
  15. 2026-09-30 20:14 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-30 06:45 UTCEG score recompute
  18. 2026-09-30 06:45 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-29 14:35 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-09-29 01:35 UTCEG score recompute
  22. 2026-09-29 01:35 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-28 12:41 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-09-27 23:51 UTCEG score recompute
  26. 2026-09-27 23:51 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  27. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-27 10:58 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-09-26 22:02 UTCEG score recompute
  30. 2026-09-26 22:02 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-25 11:46 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-09-24 22:23 UTCEG score recompute
  34. 2026-09-24 22:23 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-09-24 09:33 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-09-23 20:43 UTCEG score recompute
  37. 2026-09-23 20:43 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-09-23 07:53 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-09-22 19:04 UTCEG score recompute
  40. 2026-09-22 19:04 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-09-22 04:05 UTCEG score recompute
  42. 2026-09-22 04:05 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-09-21 15:14 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-09-21 02:17 UTCEG score recompute
  45. 2026-09-21 02:16 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-09-20 13:25 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-09-20 00:34 UTCEG score recompute
  48. 2026-09-20 00:34 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-09-19 11:45 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-09-18 22:47 UTCEG score recompute
  51. 2026-09-18 22:47 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-09-18 09:58 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-09-17 21:08 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-17 04:54 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-09-16 16:04 UTCEG score recompute
  57. 2026-09-16 16:04 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-09-16 03:13 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-09-15 14:23 UTCEG score recompute
  62. 2026-09-15 14:23 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-09-15 01:33 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-09-14 12:43 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-13 23:45 UTCEG score recompute
  66. 2026-09-13 23:45 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  68. 2026-09-13 10:56 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-09-12 22:06 UTCEG score recompute
  70. 2026-09-12 22:06 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  72. 2026-09-12 09:13 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-09-11 20:23 UTCEG score recompute
  74. 2026-09-11 20:23 UTCGHSA enrichmentGHSA-p3x9-7mrv-5rx5 · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16233?
CVE-2026-16233 is a high-severity vulnerability; its CVE record was published on August 25, 2026. There is a memory corruption vulnerability recently discovered in NI LabVIEW 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 2026 Q3 (26.3.0) and…
When was the CVE record for CVE-2026-16233 published?
The CVE record for CVE-2026-16233 was published on August 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-16233 actively exploited?
CVE-2026-16233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16233?
CVE-2026-16233 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16233?
A fix for CVE-2026-16233 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-16233 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16233

Explore →

Is Your Infrastructure Affected by CVE-2026-16233?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs