CVE-2026-1530: Fog-kubevirt: fog-kubevirt: man-in-the-middle vulnerability due to disabled certificate validation

Published Jan 28, 2026
·
Updated

A flaw was found in fog-kubevirt. This vulnerability allows a remote attacker to perform a Man-in-the-Middle (MITM) attack due to disabled certificate validation. This enables the attacker to intercept and potentially alter sensitive communications between Satellite and OpenShift, resulting in information disclosure and data integrity compromise.

Other sources

Summary: MITM in fog-kubevirt due disabled certificate validation

Requirements to exploit: Being able to MITM traffic between Satellite and OpenShift

Component affected: https://github.com/fog/fog-kubevirt

Version affected: <= 1.5.0

Patch available: no

Version fixed (if any already): none

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 with any CA cert provided See that connections succeed, even if the CA is wrong Mitigation if available: None

Original report: this email

When foremankubevirt sets up a new client, it passes in the CA provided in the UI to Fog::Kubevirt::Compute [1]. This CA (and the boolean whether SSL verification should happen at all), is then used in obtainssloptions to prepare the SSL options for kubeclient [2][3]. However, when the client is actually created, @opts is overridden and contains verifyssl => OpenSSL::SSL::VERIFYNONE [4].

— Red Hat

Affected Software

3 affected componentsFixes available
github/fog/fog-kubevirt<=1.5.0
rubygems/fog-kubevirt<1.5.1
1.5.1
IBM API Connect<=V10.0.8.0 - V10.0.8.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rubygems/fog-kubevirt to a version that resolves this vulnerability.

    Fixed in 1.5.1
  2. Configuration

    Change fog-kubevirt to enable certificate validation so it does NOT set verify_ssl => OpenSSL::SSL::VERIFY_NONE when using obtain_ssl_options/kubeclient. Ensure the provided CA cert is used for verifying the Satellite↔OpenShift KubeVirt TLS connection.

    fog-kubevirt (foreman_kubevirt / Fog::Kubevirt::Compute) verify_ssl (SSL verification) = OpenSSL::SSL::VERIFY_NONE

Event History

Jan 28, 2026
Data Sourced
via Red Hat·12:42 PM
DescriptionSeverityAffected Software
Feb 2, 2026
CVE Published
via MITRE·05:47 AM
Data Sourced
via MITRE·05:47 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:30 AM
Data Sourced
via GitHub·06:30 AM
DescriptionSeverityWeaknessAffected Software
Nov 18, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments using fog-kubevirt version 1.5.0 or earlier in communications between Satellite and OpenShift are affected. The reported affected use case is configuring OpenShift Virtualization or KubeVirt in Satellite.

2

What must an attacker be able to do to exploit it?

The attacker must be able to perform a man-in-the-middle attack on traffic between Satellite and OpenShift. No user interaction is required, but the CVSS vector indicates low privileges are required.

3

Are incorrect CA certificates rejected?

No. Connections can succeed even when the CA certificate supplied during OpenShift Virtualization or KubeVirt configuration is incorrect, because certificate validation is disabled.

4

Is a patch or workaround available?

No patch, fixed version, or mitigation is provided in the available data.

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