CVE-2026-11347

CVE-2026-11347 is a high-severity vulnerability with a CVSS 4.0 base score of 8.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-11347?
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.
How severe is CVE-2026-11347?
CVE-2026-11347 has a CVSS 4.0 base score of 8.5, rated high severity.
Is CVE-2026-11347 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-11347?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-11347 have an EU (EUVD) identifier?
Yes. CVE-2026-11347 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-34811.
When was CVE-2026-11347 published?
CVE-2026-11347 was published on 2026-06-05 and last updated on 2026-06-17.

References

Other CWE-321 vulnerabilities

Browse all CWE-321 vulnerabilities →