CVE-2026-82618

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-08-31. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability was determined in Systerel S2OPC up to 1.7.3. The affected element is the function set_range_matrix_on_string_array of the file src/Common/opcua_types/sopc_builtintypes.c of the component String Array Range Writing. This manipulation causes out-of-bounds read. The attack is possible to be carried out remotely. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 31, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Aug 31, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Server-side heap out-of-bounds read in two-dimensional IndexRange writes to String[] (#1796) · Issues · Systerel / S2OPC · GitLab

https://gitlab.com/systerel/S2OPC/-/work_items/1796

Vendor Advisories for CVE-2026-82618(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-24 14:04 UTCEPSS rescore
  2. 2026-09-24 12:48 UTCEG score recompute
  3. 2026-09-24 12:48 UTCGHSA enrichment
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 11:03 UTCEG score recompute
  6. 2026-09-23 11:03 UTCGHSA enrichment
  7. 2026-09-22 16:01 UTCEPSS rescore
  8. 2026-09-22 09:18 UTCEG score recompute
  9. 2026-09-22 09:18 UTCGHSA enrichment
  10. 2026-09-21 21:09 UTCEPSS rescore
  11. 2026-09-21 07:31 UTCEG score recompute
  12. 2026-09-21 07:31 UTCGHSA enrichment
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-20 05:26 UTCEG score recompute
  15. 2026-09-20 05:26 UTCGHSA enrichment
  16. 2026-09-19 03:41 UTCEG score recompute
  17. 2026-09-19 03:41 UTCGHSA enrichment
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 01:56 UTCEG score recompute
  20. 2026-09-18 01:56 UTCGHSA enrichment
  21. 2026-09-17 00:11 UTCEG score recompute
  22. 2026-09-17 00:11 UTCGHSA enrichment
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-15 22:26 UTCEG score recompute
Show 45 more
  1. 2026-09-15 22:26 UTCGHSA enrichment
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-15 03:12 UTCEPSS rescore
  4. 2026-09-14 20:40 UTCGHSA enrichment
  5. 2026-09-13 18:55 UTCEG score recompute
  6. 2026-09-13 18:55 UTCGHSA enrichment
  7. 2026-09-12 17:06 UTCEG score recompute
  8. 2026-09-12 17:06 UTCGHSA enrichment
  9. 2026-09-11 15:21 UTCEG score recompute
  10. 2026-09-11 15:21 UTCGHSA enrichment
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-10 13:36 UTCEG score recompute
  14. 2026-09-10 13:36 UTCGHSA enrichment
  15. 2026-09-09 11:51 UTCEG score recompute
  16. 2026-09-09 11:51 UTCGHSA enrichment
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 10:06 UTCEG score recompute
  19. 2026-09-08 10:06 UTCGHSA enrichment
  20. 2026-09-07 07:38 UTCEG score recompute
  21. 2026-09-07 07:38 UTCGHSA enrichment
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-06 05:51 UTCEG score recompute
  24. 2026-09-06 05:51 UTCGHSA enrichment
  25. 2026-09-05 15:31 UTCEPSS rescore
  26. 2026-09-05 04:06 UTCEG score recompute
  27. 2026-09-05 04:06 UTCGHSA enrichment
  28. 2026-09-04 05:07 UTCEPSS rescore
  29. 2026-09-04 02:21 UTCGHSA enrichment
  30. 2026-09-03 00:34 UTCEG score recompute
  31. 2026-09-03 00:34 UTCGHSA enrichment
  32. 2026-09-02 14:12 UTCEPSS rescore
  33. 2026-09-01 22:48 UTCEG score recompute
  34. 2026-09-01 22:48 UTCGHSA enrichment
  35. 2026-09-01 13:54 UTCEPSS rescore
  36. 2026-09-01 04:40 UTCEPSS rescore
  37. 2026-09-01 04:40 UTCEPSS rescore
  38. 2026-08-31 21:03 UTCGHSA enrichment
  39. 2026-08-31 17:24 UTCEG score recompute
  40. 2026-08-31 17:24 UTCGHSA enrichment
  41. 2026-08-31 16:39 UTCEG score recompute
  42. 2026-08-31 16:39 UTCGHSA enrichment
  43. 2026-08-31 05:24 UTCEG score recompute
  44. 2026-08-31 05:06 UTCEG score recompute
  45. 2026-08-31 05:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82618?
CVE-2026-82618 is a medium vulnerability published on August 31, 2026. A vulnerability was determined in Systerel S2OPC up to 1.7.3. The affected element is the function setrangematrixonstringarray of the file src/Common/opcuatypes/sopc_builtintypes.c of the component String Array Range Writing. This manipulation causes out-of-bounds read. The attack is possible to be…
When was CVE-2026-82618 disclosed?
CVE-2026-82618 was first published in the National Vulnerability Database on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82618 actively exploited?
CVE-2026-82618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.0% of all scored CVEs.
What is the CVSS score of CVE-2026-82618?
CVE-2026-82618 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-82618?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82618, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82618?

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

Book a Demo →Browse All CVEs