top of page

VMware Aria Operations and VCF Operations Workaround for VMSA-2026-0010

Writer: Brock Peterson
Brock Peterson
10 hours ago
2 min read

VMSA-2026-0010: Apache HTTP Server mod_http2 heap corruption remote code execution vulnerability (CVE-2026-119618) was published yesterday affecting VMware Aria Operations 8.18.x and 9.x.x.x. With a Fixed Version pending, let's apply the work around listed in the KB.


I'll start with my VMware Aria Operations 8.18.7 lab. I've confirmed SSH is enabled on my Operations Cluster Nodes via the admin UI. I've also taken Snaphots of the VMs just to be safe. I've downloaded the script in the above KB.



As instructed, once downloaded, upload it to /root on your Primary Node. Then run this:

bash /root/cve-2026-119618_v2.sh --check --node primary_node_goes_here

The output will look something like this.

NODE                                          APACHE   CVE FIX  HTTP/2  ALPN      RESULT
vcfops-135-126.vcfops.lab                     2.4.66   no       on      h2        AFFECTED, run --apply
vcfops-135-128.vcfops.lab                     2.4.66   no       on      h2        AFFECTED, run --apply

As instructed by the KB, if any of the Nodes are affected, apply the workaround by running this.

bash /root/cve-2026-119618_v2.sh --apply --node any_node_goes_here

The output will look something like this at the end.

NODE                                          APACHE   CVE FIX  HTTP/2  ALPN      RESULT
vcfops-135-126.vcfops.lab                     2.4.66   no       off     http/1.1  workaround applied
vcfops-135-128.vcfops.lab                     2.4.66   no       off     http/1.1  workaround applied

As you can see, the workaround has been applied.


Let's do the VCF Operations 9.0.2 lab next. SCP the script up to it into the same /root location and run this:

bash /root/cve-2026-119618_v2.sh --check --node primary_node_goes_here

The output will look something like this.

NODE                                          APACHE   CVE FIX  HTTP/2  ALPN      RESULT
192.168.135.113                               2.4.66   no       on      h2        AFFECTED, run --apply

As instructed by the KB, if any of the Nodes are affected, apply the workaround by running this.

bash /root/cve-2026-119618_v2.sh --apply --node any_node_goes_here

The output for this Operations 9.0.2 environment looks like this.

NODE                                          APACHE   CVE FIX  HTTP/2  ALPN      RESULT
192.168.135.113                               2.4.66   no       off     http/1.1  workaround applied

As you can see, the workaround has been applied.



Let's do the VCF Operations 9.1.1 lab next. SCP the script up to it into the same /root location and run this:

bash /root/cve-2026-119618_v2.sh --check --node primary_node_goes_here

The output will look something like this.

NODE                                          APACHE   CVE FIX  HTTP/2  ALPN      RESULT
vcfops-135-110.vcfops.lab                     2.4.68   no       on      h2        AFFECTED, run --apply
vcfops-135-115.vcfops.lab                     2.4.68   no       on      h2        AFFECTED, run --apply

As you can see, this environment has two nodes, we'll apply the workaround like we did previously by running this.

bash /root/cve-2026-119618_v2.sh --apply --node any_node_goes_here

The output for this Operations 9.1.1 environment looks like this.


NODE                                          APACHE   CVE FIX  HTTP/2  ALPN      RESULT
vcfops-135-110.vcfops.lab                     2.4.68   no       off     http/1.1  workaround applied
vcfops-135-115.vcfops.lab                     2.4.68   no       off     http/1.1  workaround applied

Hope this was helpful, enjoy!

Comments


Leave a Comment above or email me here with questions, thanks for reading!
    bottom of page