CVE-2026-17070

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 Accessing Functionality Not Properly Constrained by ACLs.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17070?
CVE-2026-17070 is a high vulnerability published on August 4, 2026. Missing Authorization vulnerability in HAVELSAN Inc. Liman MYS allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Liman MYS: from 2.2.3 before 2.3.1.
When was CVE-2026-17070 disclosed?
CVE-2026-17070 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-17070 actively exploited?
CVE-2026-17070 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 78.8% of all scored CVEs.
What is the CVSS score of CVE-2026-17070?
CVE-2026-17070 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-17070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17070, 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-17070

Explore →

Is Your Infrastructure Affected by CVE-2026-17070?

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

Start Free Scan →Browse All CVEs