# CVE-2026-77703: SSH Host Key Verification Bypass in HAVELSAN's Liman Render Engine

> Attackers can bypass SSH host key verification to perform man-in-the-middle attacks, intercepting or modifying data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-f9gv-cv7x-jrv2

## What is CVE-2026-77703?

CVE-2026-77703 is a medium-severity vulnerability in HAVELSAN Inc. Liman Render Engine, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-322 (Key Exchange without Entity Authentication)

## Which versions are affected by CVE-2026-77703?


## How do I fix CVE-2026-77703?

No fix has been published for CVE-2026-77703 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77703 being exploited?

There is no known exploitation of CVE-2026-77703 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77703 and fix it if it is affected.

What it is: CVE-2026-77703 is a medium-severity vulnerability in HAVELSAN Inc. Liman Render Engine, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77703 in the wild and no public exploit code.

Affected product: HAVELSAN Inc. Liman Render Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77703/ (Markdown: https://insights.sbomify.com/CVE-2026-77703/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77703
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77703
- OSV: https://osv.dev/vulnerability/CVE-2026-77703

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77703/
Summaries are generated and may contain mistakes; the official description above is the record.