CVE-2026-11946

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
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: None knownExposed: 0

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

An unauthenticated remote attacker can exhaust server memory via the GetEndpoints Discovery Service in open62541. The endpointUrl field of GetEndpointsRequest is not validated for length. An attacker can declare an arbitrarily large string (up to ~4.09 GB via the UInt32 length field) delivered across intermediate chunks without ever sending the final chunk. The server buffers all chunks in RAM indefinitely until the SecureChannel times out. The attack is pre-session and bypasses all encryption configurations.

The issue affects open62541: from 1.4.0 through 1.4.16, from 1.5.0 through 1.5.4, master.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (3)

Auto-updated Jul 3, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

fix(server): Enforce default message and chunk size limits to prevent DoS

Patch available: open62541/open62541 v1.4.17 (PR #8142 merged 2026-06-23)

https://github.com/open62541/open62541/pull/8142/changes/d253818d6c5e870e1db0e360b18138c8bdc809ae
github_pr Patch Available

fix(server): Enforce default message and chunk size limits to prevent DoS

Patch available: open62541/open62541 v1.4.17 (PR #8142 merged 2026-06-23)

https://github.com/open62541/open62541/pull/8142
generic

GitHub - open62541/open62541: Open source implementation of OPC UA (OPC Unified Architecture) aka IEC 62541 licensed under Mozilla Public License v2.0 · GitHub

https://github.com/open62541/open62541

Vendor Advisories for CVE-2026-11946(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 13× in last 7d / 62× 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-07-27 00:55 UTCEG score recompute
  2. 2026-07-27 00:55 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 13:08 UTCEG score recompute
  6. 2026-07-26 13:08 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:05 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:30 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-17 06:33 UTCGHSA enrichment
  18. 2026-07-16 18:46 UTCGHSA enrichment
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-16 06:59 UTCGHSA enrichment
  21. 2026-07-15 19:12 UTCGHSA enrichment
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 07:25 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-14 19:38 UTCGHSA enrichment
Show 37 more
  1. 2026-07-14 07:48 UTCGHSA enrichment
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 20:01 UTCGHSA enrichment
  4. 2026-07-13 08:14 UTCGHSA enrichment
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-12 20:26 UTCGHSA enrichment
  7. 2026-07-12 08:39 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 20:52 UTCGHSA enrichment
  10. 2026-07-11 09:05 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-10 21:18 UTCGHSA enrichment
  13. 2026-07-10 09:32 UTCGHSA enrichment
  14. 2026-07-09 21:44 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 09:57 UTCGHSA enrichment
  17. 2026-07-08 22:11 UTCGHSA enrichment
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-08 10:24 UTCGHSA enrichment
  21. 2026-07-07 22:37 UTCGHSA enrichment
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-07 10:51 UTCGHSA enrichment
  24. 2026-07-06 22:43 UTCGHSA enrichment
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 10:57 UTCGHSA enrichment
  27. 2026-07-06 02:23 UTCEPSS rescore
  28. 2026-07-05 23:09 UTCGHSA enrichment
  29. 2026-07-05 11:18 UTCGHSA enrichment
  30. 2026-07-04 23:31 UTCGHSA enrichment
  31. 2026-07-04 11:44 UTCGHSA enrichment
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-03 23:56 UTCGHSA enrichment
  34. 2026-07-03 12:09 UTCGHSA enrichment
  35. 2026-07-03 00:22 UTCGHSA enrichment
  36. 2026-07-02 12:36 UTCEG score recompute
  37. 2026-07-02 12:36 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-11946?
CVE-2026-11946 is a high vulnerability published on July 2, 2026. An unauthenticated remote attacker can exhaust server memory via the GetEndpoints Discovery Service in open62541. The endpointUrl field of GetEndpointsRequest is not validated for length. An attacker can declare an arbitrarily large string (up to ~4.09 GB via the UInt32 length field) delivered…
When was CVE-2026-11946 disclosed?
CVE-2026-11946 was first published in the National Vulnerability Database on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11946 actively exploited?
CVE-2026-11946 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 69.3% of all scored CVEs.
What is the CVSS score of CVE-2026-11946?
CVE-2026-11946 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-11946?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11946, 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-11946

Explore →

Is Your Infrastructure Affected by CVE-2026-11946?

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

Start Free Scan →Browse All CVEs