CVE-2026-54548

kas: Persistent SSH Host Key Checking Disablement

Published Aug 26, 2026 CVSS 3.1 · 3.3 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

kas, a tool for setting up BitBake projects, creates a global SSH configuration rule when no user‑specific configuration exists. During this process the tool writes "StrictHostKeyChecking no" into a newly created ~/.ssh/config. Because the rule remains in the configuration file after kas exits, any subsequent SSH session by the same local user inherits the disabled host key check, allowing an attacker who can control the remote SSH host key or server to mount a man‑in‑the‑middle attack without detection. The weakness is categorized as CWE‑295, an improper restriction of administrative attributes that permits manipulation of security‑critical settings.

Affected Systems

The affected product is Siemens kas. All kas releases prior to version 5.4 are vulnerable. No specific sub‑version list is provided, but the issue is fixed in the 5.4 release and later, so any earlier deployment is at risk.

Risk and Exploitability

The CVSS score is 3.3, indicating low severity. EPSS data is unavailable and the vulnerability is not in the CISA KEV catalog, suggesting a low likelihood of exploitation. The attack vector is inferred to be local: it requires kas to run in a CI or user environment that subsequently initiates SSH connections. An attacker would need to control the remote SSH host or supply a malicious host key to benefit from the disabled host key verification. Therefore, while the vulnerability alone is not immediately dangerous, it can be leveraged to facilitate man‑in‑the‑middle attacks for attackers who can influence future SSH sessions made by the vulnerable user.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Siemens kas to version 5.4 or later
  • If upgrading is not possible, delete or remove the global Host * rule containing "StrictHostKeyChecking no" from the user's ~/.ssh/config
  • Configure kas to use a user‑specific SSH configuration or run kas in a controlled environment that does not create global SSH settings

Generated by OpenCVE AI on August 26, 2026 at 17:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-mv8m-v9v6-5f94 kas Persistently Disables SSH Host Key Checking
History
Type Values Removed Values Added
First Time appeared Siemens
Siemens kas
Vendors & Products Siemens
Siemens kas
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title kas: Persistent SSH Host Key Checking Disablement
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 26, 2026, 3:36 PM
Reserved
Jun 15, 2026, 7:04 PM
Status
Deferred
Published
Aug 26, 2026, 3:16 PM
Modified
Sep 9, 2026, 9:09 PM