CVE-2026-11345

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS

Also known asEUVD-2026-34824 (ENISA EUVD) · GHSA-xj32-w24w-7c6q (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.9Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (linqi GmbH) lists linqi GmbH linqi versions before 1.4.8.6 as affected. No release containing a fix is confirmed on record.

An Improper Authentication vulnerability in the /api/Cdn/GetFile endpoint of linqi allows unauthenticated, remote attackers to bypass file access controls. The ValidateAnonFileAccess function incorrectly grants access if an 'AnonFile' query parameter containing exactly 256 characters is provided. While this flaw allows bypassing the intended authorization check, the actual security impact is negligible; the exposed resources are strictly limited to minified JavaScript and CSS files that contain no sensitive data and are already publicly accessible via a standard CDN.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 5, 2026

Last Modified

June 5, 2026

Advisory Details (1)

Auto-updated Jun 14, 2026
No fix on record yet.

Vendor Advisories for CVE-2026-11345(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 8× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-10-25 14:51 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-23 07:54 UTCEG score recompute
  11. 2026-10-23 07:54 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  12. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-18 05:05 UTCEG score recompute
  18. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-12 16:37 UTCEG score recompute
  24. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-11 20:13 UTCEG score recompute
Show 75 more
  1. 2026-10-11 18:25 UTCEG score recompute
  2. 2026-10-11 14:59 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-14 05:03 UTCEG score recompute
  22. 2026-09-14 05:03 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  23. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-08-25 01:59 UTCEG score recompute
  41. 2026-08-25 01:59 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  42. 2026-08-23 12:27 UTCEG score recompute
  43. 2026-08-23 12:27 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  44. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-08-21 12:47 UTCEG score recompute
  47. 2026-08-21 12:47 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  48. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-08-20 09:42 UTCEG score recompute
  50. 2026-08-20 09:42 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-08-16 14:53 UTCEG score recompute
  55. 2026-08-16 14:53 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-08-15 13:17 UTCEG score recompute
  58. 2026-08-15 13:17 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-08-14 11:24 UTCEG score recompute
  61. 2026-08-14 11:24 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  62. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  63. 2026-08-13 09:49 UTCEG score recompute
  64. 2026-08-13 09:49 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  65. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  66. 2026-08-12 08:12 UTCEG score recompute
  67. 2026-08-12 08:12 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  68. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  69. 2026-08-11 04:19 UTCEG score recompute
  70. 2026-08-11 04:19 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  71. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  72. 2026-08-10 02:43 UTCEG score recompute
  73. 2026-08-10 02:43 UTCGHSA enrichmentGHSA-xj32-w24w-7c6q
  74. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  75. 2026-08-09 01:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-11345?
CVE-2026-11345 is a medium-severity vulnerability; its CVE record was published on June 5, 2026. An Improper Authentication vulnerability in the /api/Cdn/GetFile endpoint of linqi allows unauthenticated, remote attackers to bypass file access controls. The ValidateAnonFileAccess function incorrectly grants access if an 'AnonFile' query parameter containing exactly 256 characters is provided.…
When was the CVE record for CVE-2026-11345 published?
The CVE record for CVE-2026-11345 was published on June 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 5, 2026; the record at its source may have been updated since.
Is CVE-2026-11345 actively exploited?
CVE-2026-11345 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11345?
CVE-2026-11345 has a CVSS base score of 6.9 (the CNA's own assessment, by linqi; NVD's own analysis pending).
How do I remediate CVE-2026-11345?
No fix for CVE-2026-11345 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (linqi GmbH) lists linqi GmbH linqi versions before 1.4.8.6 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-11345 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11345?

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