CVE-2026-1531: Foreman-kubevirt: foreman_kubevirt: man-in-the-middle due to insecure default ssl verification
A flaw was found in foremankubevirt. When configuring the connection to OpenShift, the system disables SSL verification if a Certificate Authority (CA) certificate is not explicitly set. This insecure default allows a remote attacker, capable of intercepting network traffic between Satellite and OpenShift, to perform a Man-in-the-Middle (MITM) attack. Such an attack could lead to the disclosure or alteration of sensitive information.
Other sources
Summary: MITM in foremankubevirt due to insecure defaults
Requirements to exploit: Being able to MITM traffic between Satellite and OpenShift
Component affected: https://github.com/theforeman/foremankubevirt
Version affected: <= 0.4.0
Patch available: no
Version fixed (if any already): N/A
CVSS (optional): N/A
Impact (optional): Important
Embargo: No
Reason: The amount of affected systems should be low Suggested public date: dd-MMM-yyyy
Acknowledgement: Evgeni Golov
Steps to reproduce if available:
Configure OpenShift Virtualization / KubeVirt in Satellite and don't enter anything in the CA field Mitigation if available: Explicitly set a CA
Original report: this email
When foremankubevirt configures the connection to OpenShift, it only enables kubevirtverifyssl when a CA certificate was explicitly set in the settings [1]. Normally, users would expect that the system trust store is used when no explicit CA was set. But in this case the whole verification is disabled instead.
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rubygems/foreman_kubevirtto a version that resolves this vulnerability.Fixed in 0.4.3 - Configuration
When configuring the connection to OpenShift in Satellite for foreman_kubevirt, explicitly provide a CA certificate in the CA field so that foreman_kubevirt enables kubevirt_verify_ssl (i.e., avoid the insecure default where SSL verification is disabled when no CA is explicitly set).
foreman_kubevirt (Foreman-kubevirt) / OpenShift/KubeVirt connection kubevirt_verify_ssl = enabled only when a CA certificate is explicitly set (disable SSL verification if CA is not set)
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using foreman_kubevirt version 0.4.0 or earlier may be exposed when OpenShift Virtualization or KubeVirt is configured in Satellite without a CA certificate entered in the CA field.
What does an attacker need to exploit this vulnerability?
An attacker must be able to intercept network traffic between Satellite and OpenShift. No user interaction is required, but the attacker needs a network position that permits a man-in-the-middle attack.
How can I mitigate the issue if no patch is available?
Explicitly configure a CA certificate for the OpenShift connection in Satellite. This enables certificate validation instead of relying on the insecure behavior when the CA field is left empty.
How can I determine whether my configuration is affected?
Review the OpenShift Virtualization or KubeVirt connection configuration in Satellite. If the CA field is empty, SSL verification is disabled and the connection is affected.