CVE-2026-54548

published 26 Aug 2026 · updated 26 Aug 2026

kas: Persistent SSH Host Key Checking Disablement

3.3LowCVSS 3.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

kas is a setup tool for bitbake based projects. Prior to 5.4, internal SSH key setup triggered by SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE creates ~/.ssh/config when no user-specific SSH configuration exists and adds a global Host * rule containing StrictHostKeyChecking no. In kas/libcmds.py, ssh_no_host_key_check() runs without checking ctx.managed_env, so the setting persists after kas exits and affects future SSH sessions by the same local user, extending beyond the intended short-lived continuous integration environment. A later SSH connection can therefore accept an attacker-controlled host key without verification, increasing the risk of a man-in-the-middle attack that compromises session confidentiality or integrity. This issue is fixed in version 5.4.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Siemenskas<5.4

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Siemens, strongest first

10.0CriticalCISA KEVPublic exploit
10.0CriticalCISA KEVPublic exploit

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-54548 severity on Zeptric[![CVE-2026-54548](https://zeptric.io/badge/cve/CVE-2026-54548.svg)](https://zeptric.io/cve/CVE-2026-54548)