CVE-2026-11826

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-18. A secondary CVSS source baseline 8.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

Also known asEUVD-2026-45380 (ENISA EUVD) · GHSA-3x22-r5w3-j249 (GitHub Security Advisories)Source: ENISA EUVD

8.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.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

OpenPLC_v3 contains a heap-based buffer overflow in the getData() function in webserver/core/modbus_master.cpp. getData() reads characters between two delimiters into a caller-supplied buffer with no size parameter and no bounds check. In parseConfig() the function is invoked with the 100-byte heap-allocated MB_device.dev_name field. An authenticated attacker with access to the OpenPLC web interface can send a crafted HTTP POST to the /modbus endpoint with an oversized device_name value; the value is persisted to mbconfig.cfg and parsed on load, overflowing dev_name and overwriting adjacent struct fields (protocol at offset 108, dev_address at offset 109, ip_port at offset 210). A 200-byte payload writes 100 bytes past the allocation. The result is heap corruption leading to runtime crash and denial of service of the PLC process control loop, with attacker-controlled overwrite of adjacent configuration fields. The upstream repository was archived on 2026-04-04 and no fix is expected; the vendor has confirmed the issue does not affect OpenPLC Runtime v4.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

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

July 18, 2026

Last Modified

October 24, 2026

Advisory Details (4)

Auto-updated Jul 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

OpenPLC_v3 Heap-Based Buffer Overflow in Modbus Master getData() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openplc-v3-heap-based-buffer-overflow-in-modbus-master-getdata
GitHub commit

commit b4702061dc14 (thiagoralves/OpenPLC_v3)

Fix landed in thiagoralves/OpenPLC_v3 commit b4702061dc14 — awaiting tagged release

https://github.com/thiagoralves/OpenPLC_v3/commit/b4702061dc14d1024856f71b4543298d77007b88
Web page

GitHub - thiagoralves/OpenPLC_v3: OpenPLC Runtime version 3 · GitHub

https://github.com/thiagoralves/OpenPLC_v3
Web page

Security Vulnerability Report: Heap Buffer Overflow in getData() — openplcproject/OpenPLC_v3 (CWE-122, CVSS 8.8 HIGH) · GitHub

https://gist.github.com/Shukhrat-03/5cf1825b72e485ef98a32958dfbc611a#security-vulnerability-report

Vendor Advisories for CVE-2026-11826(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 12× in last 7d / 45× 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 230 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 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-11826?
CVE-2026-11826 is a high-severity vulnerability; its CVE record was published on July 18, 2026. OpenPLCv3 contains a heap-based buffer overflow in the getData() function in webserver/core/modbusmaster.cpp. getData() reads characters between two delimiters into a caller-supplied buffer with no size parameter and no bounds check. In parseConfig() the function is invoked with the 100-byte…
When was CVE-2026-11826 made public?
CVE-2026-11826 was made public on July 17, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 18, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-11826 actively exploited?
CVE-2026-11826 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11826?
CVE-2026-11826 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11826?
An upstream fix for CVE-2026-11826 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-11826 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11826?

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