BugZero | VMware vCenter BugID 4951d9d85582 - Upgrading vCenter Server using the CLI incorrectly...

VMware vCenter - Defect ID: 4951d9d85582

Upgrading vCenter Server using the CLI incorrectly preserves the Transport Security Layer (TLS) configuration for the vSphere Authentication Proxy service

VMware vCenter - Defect ID: 4951d9d85582

Upgrading vCenter Server using the CLI incorrectly preserves the Transport Security Layer (TLS) configuration for the vSphere Authentication Proxy service

Last updated on January 19th, 2026

BugZero Risk Score
0.0 Coming soon

Overall: N/A

Severity: N/A

Community: N/A

Lifecycle: N/A

What is the BugZero Risk Score?

VMware vCenter Integration

Learn more about where this data comes from

VMware vCenter Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Status: Known
Impact Category: Installation, Upgrade, and Migration Issues
Workaround Available:

Description

Disclaimer

A custom bug ID has been generated as the vendor did not provide one: 4951d9d85582

Overview

If the vSphere Authentication Proxy service ( vmcam ) is configured to use a particular TLS protocol other than the default TLS 1.2 protocol, this configuration is preserved during the CLI upgrade process. By default, vSphere supports the TLS 1.2 encryption protocol. If you must use the TLS 1.0 and TLS 1.1 protocols to support products or services that do not support TLS 1.2, use the TLS Configurator Utility to enable or deactivate different TLS protocol versions. To learn how to manage TLS protocol configuration and use the TLS Configurator Utility, see the VMware Security documentation.

Workaround

Use the TLS Configurator Utility to configure the vmcam port

Bug URLs

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-70u3v-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3l-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3m-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3n-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3o-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3p-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3q-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3r-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3s-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3u-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3w-release-notes.html

Relevant Products

Click on a version to see all relevant bugs

Affected versions:7.0.3.01400, 7.0.3.01500, 7.0.3.01600, 7.0.3.01700, 7.0.3.01800, 7.0.3.01900, 7.0.3.02000, 7.0.3.02100, 7.0.3.02300, 7.0.3.02400, 7.0.3.02500

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Affected versions:7.0.3.01400, 7.0.3.01500, 7.0.3.01600, 7.0.3.01700, 7.0.3.01800, 7.0.3.01900, 7.0.3.02000, 7.0.3.02100, 7.0.3.02300, 7.0.3.02400, 7.0.3.02500

Fixed versions: No known fixed versions

Top VMware vCenter Defects

Defect ID: 3602673
Tasks for cloning and export to a content library might fail if you restrict network packets that use plain text
Defect ID: 3488172
Login instructions for RSA SecurID Authentication in the vSphere Client might display HTML tags as plain text
Defect ID: 3484244
A rare race condition might cause repeating failovers due to a failure of the vCenter vpxd service or vSphere Client becoming unresponsive
Defect ID: 68adfd8f5272
vSphere Storage vMotion operations might fail in a vSAN environment due to an unauthenticated session of the Network File Copy (NFC) manager
Defect ID: 524f315fc61b
You see large threadmonitor<num>.log files in the vsphere-ui logs directory

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: 4951d9d85582

Upgrading vCenter Server using the CLI incorrectly preserves the Transport Security Layer (TLS) configuration for the vSphere Authentication Proxy service

VMware vCenter - Defect ID: 4951d9d85582

Upgrading vCenter Server using the CLI incorrectly preserves the Transport Security Layer (TLS) configuration for the vSphere Authentication Proxy service

Last updated on January 19th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Disclaimer

Overview

Workaround

Bug URLs

Top VMware vCenter Defects

Ready to prevent the next vendor outage?

Links

BugZero Risk Score
0.0 Coming soon