Categories
CVE-2026-77703 medium CVSS 5.9

Vulnerability in Liman Render Engine (CVE-2026-77703)

Summary

Vulnerability in Liman Render Engine (CVE-2026-77703). Confidential information can be exposed externally.

Original description

The description as published by the source.

Key exchange without entity authentication vulnerability in HAVELSAN Inc. Liman Render Engine allows Adversary in the Middle (AiTM).

This issue affects Liman Render Engine: from 1.0 before 1.2-75.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77703 has been found in Liman Render Engine.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Liman Render Engine CVE-2026-77703" on the vendor's site.

CVE-2026-77703 (Liman Render Engine) — CWE-322 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-322) exists in Liman Render Engine.

📍 Affected scope

Check the vendor advisory for the affected versions of Liman Render Engine.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Liman Render Engine を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details