REDHAT-BUG-2433786: High severity github/theforeman/foreman_kubevirt vulnerability

Published Jan 28, 2026
·
Updated

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.

Affected Software

1 affected component
github/theforeman/foreman_kubevirt<=0.4.0

Event History

Jan 28, 2026
Data Sourced
via Red Hat·12:52 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using foreman_kubevirt version 0.4.0 or earlier to configure an OpenShift Virtualization or KubeVirt connection in Satellite are exposed when the CA field is left empty. The reported number of affected systems is expected to be low.

2

What access does an attacker need?

An attacker must be able to perform a man-in-the-middle attack on traffic between Satellite and OpenShift.

3

Does leaving the CA field blank use the system trust store?

No. In the affected configuration, leaving the CA field blank disables SSL verification rather than using the system trust store.

4

What can be done if an update is not available?

Explicitly configure a CA certificate in the relevant CA field. This causes certificate verification to be enabled for the OpenShift connection.

5

How can I identify an affected configuration?

Check whether foreman_kubevirt is version 0.4.0 or earlier and whether its OpenShift Virtualization or KubeVirt connection has no CA configured. A blank CA field is the condition that disables verification.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203