CVE-2026-18650

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Missing Authorization vulnerability in HAVELSAN Inc. Liman MYS allows Privilege Escalation.

This issue affects Liman MYS: from 2.2.3 before 2.3.1.

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

Published

August 4, 2026

Last Modified

August 4, 2026

Advisory Details (1)

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

T.C. Siber Güvenlik Başkanlığı

https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0741

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18650?
CVE-2026-18650 is a high vulnerability published on August 4, 2026. Missing Authorization vulnerability in HAVELSAN Inc. Liman MYS allows Privilege Escalation. This issue affects Liman MYS: from 2.2.3 before 2.3.1.
When was CVE-2026-18650 disclosed?
CVE-2026-18650 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18650 actively exploited?
CVE-2026-18650 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 85.7% of all scored CVEs.
What is the CVSS score of CVE-2026-18650?
CVE-2026-18650 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-18650?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18650, 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-18650

Explore →

Is Your Infrastructure Affected by CVE-2026-18650?

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

Start Free Scan →Browse All CVEs