BugZero | VMware vCenter BugID d68290dbde25 - HTTP requests from certain libraries to vSphere mi...

VMware vCenter - Defect ID: d68290dbde25

HTTP requests from certain libraries to vSphere might be rejected

VMware vCenter - Defect ID: d68290dbde25

HTTP requests from certain libraries to vSphere might be rejected

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: Miscellaneous Issues
Workaround Available:

Description

Disclaimer

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

Overview

The HTTP reverse proxy in vSphere 7.0 enforces stricter standard compliance than in previous releases. This might expose pre-existing problems in some third-party libraries used by applications for SOAP calls to vSphere. If you develop vSphere applications that use such libraries or include applications that rely on such libraries in your vSphere stack, you might experience connection issues when these libraries send HTTP requests to VMOMI. For example, HTTP requests issued from vijava libraries can take the following form: POST /sdk HTTP/1.1 SOAPAction Content-Type: text/xml; charset=utf-8 User-Agent: Java/1.8.0_221 The syntax in this example violates an HTTP protocol header field requirement that mandates a colon after SOAPAction. Hence, the request is rejected in flight. For example, developers who use the vijava library can consider using the latest version of the yavijava library instead.

Workaround

Developers leveraging noncompliant libraries in their applications can consider using a library that follows HTTP standards instead

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: 1c85aec6fb3f
VMware NSX installation or upgrade in a vSphere environment with DPUs might fail with a connectivity error
Defect ID: 3532388
In the vSphere Client, you cannot set the datetime format in Browser Default
Defect ID: 7d43a1f7e479
If you do not reboot an ESXi host after you enable or disable SR-IOV with the icen driver, when you configure a transport node in ENS Interrupt mode on that host, some virtual machines might not get DHCP addresses
Defect ID: d7c9886ee562
Pensando DPUs do not support Link Layer Discovery Protocol (LLDP) on physical switch ports of ESXi hosts
Defect ID: 627ee642d90e
You cannot create snapshots of virtual machines due to an error in the Content Based Read Cache (CBRC) that a digest operation has failed

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: d68290dbde25

HTTP requests from certain libraries to vSphere might be rejected

VMware vCenter - Defect ID: d68290dbde25

HTTP requests from certain libraries to vSphere might be rejected

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