Skip to main content
EPSS 0.1%top 99%

CVE-2026-54548: CWE-295: Improper Certificate Validation in siemens kas

0
Low
VulnerabilityCVE-2026-54548cvecve-2026-54548cwe-295
Published: 08/26/2026 (08/26/2026, 14:17:32 UTC)
Source: CVE Database V5
Vendor/Project: siemens
Product: kas

Description

The kas tool prior to version 5.4 improperly configures SSH by adding a global 'StrictHostKeyChecking no' rule to the user's SSH configuration, which disables host key verification for all SSH connections by that user. This setting persists beyond the intended short-lived environment, potentially allowing man-in-the-middle attacks on subsequent SSH sessions. The issue is fixed in kas version 5.4.

CVSS v3.1

Score 3.3low

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

Affected software

siemens

kas

Affected versions
<5.4

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/10/2026, 11:25:50 UTC

Technical Analysis

In kas versions before 5.4, the internal SSH key setup triggered by SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE creates a ~/.ssh/config file with a global 'Host *' rule that sets 'StrictHostKeyChecking no' if no user-specific SSH configuration exists. The function ssh_no_host_key_check() does not verify the context's managed environment, causing this insecure setting to persist after kas exits and affect future SSH sessions by the same user. This improper certificate validation increases the risk of man-in-the-middle attacks compromising session confidentiality and integrity. The vulnerability is addressed in kas version 5.4.

Potential Impact

The vulnerability allows an attacker to bypass SSH host key verification for all subsequent SSH connections by the affected user, increasing the risk of man-in-the-middle attacks that can compromise confidentiality and integrity of SSH sessions. The CVSS score is 3.3 (low), reflecting limited impact and attack complexity requiring local access and user interaction.

Mitigation Recommendations

This issue is fixed in kas version 5.4. Users should upgrade to version 5.4 or later to resolve this vulnerability. No other official remediation or temporary fixes are documented. Until upgraded, users should manually inspect and remove any global 'StrictHostKeyChecking no' settings in their ~/.ssh/config to prevent insecure SSH behavior.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-06-15T19:04:14.456Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6a8ef6f6acd9273b49fd6371

Added to database: 08/26/2026, 14:23:50 UTC

Last enriched: 09/10/2026, 11:25:50 UTC

Last updated: 10/10/2026, 06:48:17 UTC

Views: 61

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses