CVE-2026-67860

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

open62541 1.5.5 contains a heap-based buffer overflow in the default HistoryRead path when the default history database is used with the memory backend.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 5, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

`Heap Buffer Overflow` in open62541 HistoryRead ContinuationPoint Skip Handling · Issue #8091 · open62541/open62541 · GitHub

https://github.com/open62541/open62541/issues/8091

Vendor Advisories for CVE-2026-67860(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
open625411.4.11.1-1, 1.4.18-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
open625411.4.11.1-1, 1.4.18-1——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 68× 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-08-20 12:07 UTCGHSA enrichment
  2. 2026-08-20 00:59 UTCEG score recompute
  3. 2026-08-20 00:59 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 14:03 UTCGHSA enrichment
  6. 2026-08-19 03:03 UTCGHSA enrichment
  7. 2026-08-18 15:49 UTCEG score recompute
  8. 2026-08-18 15:48 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 02:47 UTCGHSA enrichment
  11. 2026-08-17 15:51 UTCEG score recompute
  12. 2026-08-17 15:51 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 04:55 UTCGHSA enrichment
  15. 2026-08-16 17:59 UTCEG score recompute
  16. 2026-08-16 17:59 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 07:03 UTCEG score recompute
  19. 2026-08-16 07:03 UTCGHSA enrichment
  20. 2026-08-15 20:08 UTCGHSA enrichment
  21. 2026-08-15 09:12 UTCEG score recompute
  22. 2026-08-15 09:12 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 22:16 UTCGHSA enrichment
  25. 2026-08-14 11:20 UTCGHSA enrichment
Show 43 more
  1. 2026-08-14 00:25 UTCEG score recompute
  2. 2026-08-14 00:25 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 13:29 UTCGHSA enrichment
  5. 2026-08-13 02:34 UTCGHSA enrichment
  6. 2026-08-12 15:38 UTCEG score recompute
  7. 2026-08-12 15:38 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 04:42 UTCGHSA enrichment
  10. 2026-08-11 17:46 UTCEG score recompute
  11. 2026-08-11 17:46 UTCGHSA enrichment
  12. 2026-08-11 06:41 UTCEG score recompute
  13. 2026-08-11 06:41 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 19:46 UTCGHSA enrichment
  16. 2026-08-10 08:50 UTCGHSA enrichment
  17. 2026-08-09 21:54 UTCEG score recompute
  18. 2026-08-09 21:54 UTCGHSA enrichment
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-09 10:59 UTCGHSA enrichment
  21. 2026-08-09 00:03 UTCEG score recompute
  22. 2026-08-09 00:03 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 13:07 UTCGHSA enrichment
  25. 2026-08-08 02:11 UTCEG score recompute
  26. 2026-08-08 02:11 UTCGHSA enrichment
  27. 2026-08-07 15:15 UTCGHSA enrichment
  28. 2026-08-07 04:19 UTCGHSA enrichment
  29. 2026-08-06 17:23 UTCEG score recompute
  30. 2026-08-06 17:23 UTCGHSA enrichment
  31. 2026-08-06 13:47 UTCEPSS rescore
  32. 2026-08-06 06:27 UTCEG score recompute
  33. 2026-08-06 06:27 UTCGHSA enrichment
  34. 2026-08-05 19:31 UTCEG score recompute
  35. 2026-08-05 19:31 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-05 19:01 UTCEG score recompute▲ 7.50
  39. 2026-08-05 19:01 UTCGHSA enrichment
  40. 2026-08-05 19:00 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  41. 2026-08-04 22:31 UTCNVD update
  42. 2026-08-04 22:06 UTCEG score recompute
  43. 2026-08-04 22:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67860?
CVE-2026-67860 is a high vulnerability published on August 4, 2026. open62541 1.5.5 contains a heap-based buffer overflow in the default HistoryRead path when the default history database is used with the memory backend.
When was CVE-2026-67860 disclosed?
CVE-2026-67860 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67860 actively exploited?
CVE-2026-67860 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 81.1% of all scored CVEs.
What is the CVSS score of CVE-2026-67860?
CVE-2026-67860 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-67860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67860, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67860

Explore →

Is Your Infrastructure Affected by CVE-2026-67860?

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

Start Free Scan →Browse All CVEs