linqi up to 1.4.8.5 Setting appsettings.json hard-coded key

Summaryinfo

A vulnerability classified as problematic has been found in linqi up to 1.4.8.5. This vulnerability affects unknown code of the file appsettings.json of the component Setting Handler. This manipulation causes hard-coded key. The identification of this vulnerability is CVE-2026-11347. The attack can only be executed locally. There is no exploit available.

Detailsinfo

A vulnerability was found in linqi up to 1.4.8.5. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file appsettings.json of the component Setting Handler. The manipulation with an unknown input leads to a hard-coded key vulnerability. The CWE definition for the vulnerability is CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared by Ianis Bernard. It is possible to read the advisory at linqi.help. This vulnerability is known as CVE-2026-11347 since 06/05/2026. The exploitation appears to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.

By approaching the search of inurl:appsettings.json it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-34811). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• linqi

Version

• 1.4.8.0
• 1.4.8.1
• 1.4.8.2
• 1.4.8.3
• 1.4.8.4
• 1.4.8.5

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion