Manual interim workaround for CVE-2026-119618 (Apache mod_http2 vulnerability) on VCF Operations
search cancel

Manual interim workaround for CVE-2026-119618 (Apache mod_http2 vulnerability) on VCF Operations

book

Article ID: 463005

calendar_today

Updated On:

Products

VCF Operations VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

CVE-2026-119618 is a critical remote code execution vulnerability in Apache HTTP Server mod_http2 that impacts VMware Aria Operations/VMware Cloud Foundation Operations. 

This vulnerability and its impact on the mentioned VMware products are documented in the following VMware Security Advisory (VMSA), review this document before continuing: VMSA-2026-0010

Environment

  • VMware Aria Operations 8.18.x
  • VMware Cloud Foundation Operations 9.x

Resolution

Automated Path

The script cve-2026-119618.sh performs Step 1, Step 2 and Reverting the workaround on all nodes of a cluster from a single machine.

Note: If the name is not as the above, rename it to cve-2026-119618.sh

It needs to run from an admin workstation or jump host. It connects to each node over SSH as root and works on the nodes one at a time. Nothing is copied to the nodes.

Requirements

    • A Linux or macOS machine with bash and OpenSSH. With OpenSSH older than 8.4, also install sshpass (for example apt install sshpass); otherwise ssh asks for the root password once per node.
    • SSH enabled on every cluster node, and port 22 reachable from that machine.
    • The root password of the nodes (the same on all nodes), or SSH key access as root.
    • The node FQDNs must resolve from that machine. If they do not, list the node IPs with --nodes.

How to run

    1. Copy the script attached to the article, save it as cve-2026-119618.sh on the admin workstation or jump host, and make it executable:

      chmod +x cve-2026-119618.sh
    2. Check the cluster. Pass the IP or FQDN of any cluster node. The script reads the full node list from that node:

      ./cve-2026-119618.sh --check --node <any-node-IP-or-FQDN>

      The script asks for the root password, then prints a summary for each node:

      NODE               APACHE   CVE FIX  HTTP/2  ALPN      RESULT
      ##.##.##.##         2.4.68   no       on      h2        AFFECTED, run --apply
      ##.##.##.##         2.4.68   no       on      h2        AFFECTED, run --apply
      ##.##.##.##         2.4.68   no       on      h2        AFFECTED, run --apply
    3. If any node shows AFFECTED, apply the workaround:

      ./cve-2026-119618.sh --apply --node <any-node-IP-or-FQDN>

      Type yes to confirm. On each node the script backs up the configuration file, makes the three changes from Step 2, runs httpd -t, restarts Apache and checks that HTTP/2 is no longer offered. The RESULT column must show workaround applied for every node.

    4. To revert the workaround:

      ./cve-2026-119618.sh --revert --node <any-node-IP-or-FQDN>

Options

OptionDescription
--checkReport the state of each node. Read-only. This is the default.
--applyDisable HTTP/2 on each affected node.
--revertUndo the changes made by --apply.
--node HOSTAny cluster node. The full node list is read from it.
--nodes H1,H2,...Use this list of nodes instead of reading it from the cluster.
--nodes-file FILERead the node list from a file, one node per line.
--yesDo not ask for confirmation before --apply or --revert.

For unattended runs, provide the root password in the CVE_ROOT_PASSWORD environment variable. Exit codes: 0 all nodes OK, 1 at least one node affected (--check), 2 error.

Notes

    • Before changing anything, the script checks that every node is reachable. If a node fails this check, no node is changed.
    • If httpd -t fails or Apache does not start, the script restores the backup on that node and stops. The remaining nodes are not changed.
    • Running --apply again on a node where the workaround is already in place changes nothing.
    • If a node cannot be reached over SSH during the run (for example, a mistyped password), the summary shows FAILED: SSH connection failed, node not changed and prints the command to re-run for the nodes that were not completed.
    • Backups are saved on each node as /root/vcops-photon-apache.conf.bak-CVE-2026-119618-<timestamp>. The script logs its actions on each node to /var/log/cve-2026-119618.log, and writes a local log to the directory you run it from.
    • --revert undoes only changes made by the script. If you applied the workaround manually, revert it manually.
    • After each upgrade, run --check again (see After upgrades).
    • Tested on multi-node clusters of VMware Aria Operations 8.18.6 and VCF Operations 9.x

What to expect
Collectors, agents and the API are not affected. The UI may feel slower.

After Upgrades
Future VCF Operations releases will ship with an upgraded version of Apache that includes the fix for CVE-2026-119618. However, every upgrade also replaces the shipped vcops-photon-apache.conf, so HTTP/2 is re-enabled automatically, even if you disabled it before. After each upgrade, repeat Step 1 on every node. If Apache is still not fixed, repeat Step 2. If it is fixed, leave HTTP/2 enabled.



Manual Steps Path

Step 1
: Check whether the environment is affected or not

On each node, as root:

httpd -v
rpm -q --changelog httpd | grep -i CVE-2026-119618

Possible results :

  • Apache 2.4.71 or later: the fix is included. No change is required
  • Apache 2.4.70 or earlier, and the changelog mentions CVE-2026-119618: the fix was added to the older version without changing its number. No change is required
  • Apache 2.4.70 or earlier, and the changelog shows nothing: Environment is affected. Process with steps in Step 2.

Step 2: Disable HTTP/2

Proceed with following steps on every node, because each node runs its own Apache.

  1. Back up and open the file
    cp -p /usr/lib/vmware-vcopssuite/utilities/conf/vcops-photon-apache.conf /root/vcops-photon-apache.conf.bak
    vi /usr/lib/vmware-vcopssuite/utilities/conf/vcops-photon-apache.conf
  2. Change these three lines (line numbers vary by version):
    FindChange to
    LoadModule http2_module /usr/lib64/httpd/modules/mod_http2.so#LoadModule http2_module /usr/lib64/httpd/modules/mod_http2.so
    Protocols h2 h2c http/1.1Protocols http/1.1
    H2WindowSize 983025#H2WindowSize 983025
  3. Test the configuration

    httpd -t
    The output must be Syntax OK. If that is the case, proceed restarting Apache (Step 4). If it is not, do not restart Apache; instead proceed with restoring the backup(see Reverting the workaround section).

    Restart Apache (this briefly interrupts access on that node):

    service httpd restart
  4. Verify 
    echo | openssl s_client -connect 127.0.0.1:443 -alpn h2,http/1.1 2>/dev/null | grep ALPN should print ALPN protocol: http/1.1

Reverting the workaround

To re-enable HTTP/2, restore the backup on each node where you applied the workaround, test the configuration and restart Apache:

cp -p /root/vcops-photon-apache.conf.bak /usr/lib/vmware-vcopssuite/utilities/conf/vcops-photon-apache.conf
httpd -t
service httpd restart

If the backup file is no longer available, undo the three changes from Step 2:

  1. Remove the # in front of the LoadModule and H2WindowSize lines
  2. Change Protocols http/1.1 back to Protocols h2 h2c http/1.1
  3. Run
    httpd -t
  4. Restart Apache
    service httpd restart
  5. Verify with the command from Step 2.4. It should print ALPN protocol: h2.

 

Attachments

cve-2026-119618.sh get_app