What changed
A library flaw has a different repair path inside an appliance
We covered CVE-2026-119618 when Apache fixed the critical mod_http2 flaw. Broadcom's 19 November advisory adds a separate operational question: VMware Cloud Foundation Operations, VMware Aria Operations and VCF Operations HCX can include the affected component. Broadcom says a network attacker may be able to execute code against the affected Operations products.
In the vendor's current matrix, product patches are marked pending. Broadcom provides workarounds through KB463005 for Operations and KB463022 for HCX. An administrator should follow those product instructions rather than assume the upstream Apache package can be replaced independently.
This is a follow-up to the Apache story
Defender workflow
Turn the advisory into a temporary control
- 1
Find the affected products. Identify Aria Operations, Cloud Foundation Operations and Operations HCX deployments and their versions, including management networks that are reachable only internally.
- 2
Apply the matching workaround. Use the specific Broadcom knowledge-base procedure for each product. Record where it was applied and verify the affected service restarted or changed as the procedure requires.
- 3
Track the eventual fix. Monitor VMSA-2026-0010 for fixed builds. Recheck the running product after an update and retire the temporary workaround only when Broadcom's instructions say it is safe.
Defender note
A fixed upstream package does not fix a bundled appliance
Dependency scans can identify the CVE but still leave the owner asking what to patch. This case needs a product inventory and a named person to carry the workaround forward until Broadcom publishes its appliance fix. Keep that exception visible; otherwise it can quietly outlive the patch cycle.