CVE-2026-11347

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:linqi, epss
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: NoneExposed: 0

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

The linqi application contains hardcoded cryptographic keys. Additionally, the application uses a weak algorithm with a limited ASCII charset to dynamically generate Initialization Vectors (IVs) for AES/CBC encryption, making known-plaintext attacks feasible. An attacker with local access can leverage these vulnerabilities to decrypt sensitive obfuscated strings, including ConnectionString values containing database credentials from appsettings.json.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
—
EPSS
0.1%
KEV
Not listed

Published

June 5, 2026

Last Modified

June 5, 2026

Advisory Details (1)

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

Security Advisories | linqi GmbH Documentation

https://linqi.help/en/reference/security/security-advisories/#security-advisory-hardcoded-cryptographic-keys-and-weak-iv-generation-in-linqi

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

Frequently asked(5)

What is CVE-2026-11347?
CVE-2026-11347 is a high vulnerability published on June 5, 2026. The linqi application contains hardcoded cryptographic keys. Additionally, the application uses a weak algorithm with a limited ASCII charset to dynamically generate Initialization Vectors (IVs) for AES/CBC encryption, making known-plaintext attacks feasible. An attacker with local access can…
When was CVE-2026-11347 disclosed?
CVE-2026-11347 was first published in the National Vulnerability Database on June 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-11347 actively exploited?
CVE-2026-11347 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11347?
CVE-2026-11347 has a CVSS v4.0 base score of 8.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-11347?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11347, 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-11347

Explore →

Is Your Infrastructure Affected by CVE-2026-11347?

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

Start Free Scan →Browse All CVEs