Baitaphish
Security intelligence
SearchLatest briefing
CVE Explorer

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.
Lifecycle PUBLISHED1 preserved revisionFact urn:baitaphish:canonical-cve-fact-revision:v2:08dbc7e89230f20cef964ca6b18b82dfedb8ad54f9d17d04f0ad197bfee7ace8
Known exploited
Not asserted
Disputed
No
Stale source
No
Conflicts
1

Preserved source conflicts

No provider value was silently selected as the winner.

cwe · 2 assertions

{"cweId":"CWE-338","description":"CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)","lang":"en","type":"CWE"}

  • cve_program_cvelist_v5cwe
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/problemTypes/1/descriptions/0

{"cweId":"CWE-321","description":"CWE-321: Use of Hard-coded Cryptographic Key","lang":"en","type":"CWE"}

  • cve_program_cvelist_v5cwe
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/problemTypes/0/descriptions/0

Affected products and versions

1 source assertion
{"defaultStatus":"unaffected","product":"linqi","vendor":"linqi GmbH","versions":[{"lessThanOrEqual":"1.4.8.5","status":"affected","version":"0","versionType":"custom"}]}
  • cve_program_cvelist_v5affected
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/affected/0

Provider-owned CVSS observations

1 source assertion
{"metric":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"LOCAL","baseScore":8.5,"baseSeverity":"HIGH","exploitMaturity":"NOT_DEFINED","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"HIGH","vulnConfidentialityImpact":"HIG…
  • cve_program_cvelist_v5cvss
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/metrics/0/cvssV4_0

CWE assertions

2 source assertions
{"cweId":"CWE-338","description":"CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)","lang":"en","type":"CWE"}
  • cve_program_cvelist_v5cwe
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/problemTypes/1/descriptions/0
{"cweId":"CWE-321","description":"CWE-321: Use of Hard-coded Cryptographic Key","lang":"en","type":"CWE"}
  • cve_program_cvelist_v5cwe
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/problemTypes/0/descriptions/0

Source references

1 source assertion
{"tags":["vendor-advisory"],"url":"https://linqi.help/en/reference/security/security-advisories/#security-advisory-hardcoded-cryptographic-keys-and-weak-iv-generation-in-linqi"}
  • cve_program_cvelist_v5reference
    urn:baitaphish:normalized-source-record:v2:0fa826b94293ad330c28a1198a1cdc65c97978aa9dc3718bbe444bcb89b398ab · sha256:b22ad39ce7616baa… · /containers/cna/references/0

Attribution and limitations

  • CVE Program CVEList V5: Reproduce the MITRE copyright designation and CVE license in copies. Source →

Provider severity values are preserved separately. Baitaphish does not convert them into a risk rating, infer affected products, or treat EPSS as observed exploitation.

← Back to CVE Explorer