CVE-2026-111497 is a Critical severity vulnerability that impacts SDDC manager. This vulnerability and its impact on the mentioned VMware products are documented in the following VMware Security Advisory (VMSA), review this document before continuing:
Note: If your SDDC Manager is on SDDC Manager 5.2.4, 9.0.2, 9.1.0 please follow the steps in KB, "Manual interim workaround for CVE-2026-111497 (Brotli) on SDDC Manager 5.2.4, 9.0.2, 9.1.0"
The workaround described in this document is meant to be a temporary solution only and is intended to ONLY mitigate CVE-2026-111497.
There are two solution paths outline below, Automated and Manual steps, should you face any issues with either workflow please engage VMware by Broadcom Support.
CVE-2026-111497_VCF911x_remediation.sh attached to this KB.The script has three commands. Run them as root, in this order.
1. check: Validates the appliance. It changes nothing.
Checks the SDDC Manager version, the health of the SDDC Manager UI, and whether the workaround can be applied (or is already working). Makes no changes.
2. apply: Applies the workaround.
The script checks that the SDDC Manager UI is healthy, backs up the files it changes, applies the change and reloads the sddc service. It then restarts the SDDC Manager UI and verifies the result.
3. rollback (optional): Removes the workaround. Use it only if you need to undo the change, for example because of an issue after applying it.
It removes only what the script added, reloads nginx, restarts the SDDC Manager UI and waits for it to come back.
Note: If the workaround was added by hand with the manual steps in this KB, the script makes no changes and asks you to use the manual rollback steps instead.
vcf user and then change to root.Back up the two files which will be modified, use below commands to take the backup:
/etc/nginx/nginx.conf.http { } block. * Put it after the line "map_hash_bucket_size 128": # CVE-2026-111497 interim workaround: refuse request bodies that declare
# Content-Encoding: br. Brotli is the only encoding affected by this CVE.
# Remove once the Node.js runtime is upgraded to a fixed release.
map $http_content_encoding $reject_br {
default 0;
"~*\bbr\b" 1;
}
Sample Result after the edit (Note: Command used less -N /etc/nginx/nginx.conf):
{ listen 443 ssl; ... } block.** Put it just before the # certs sent to the client in SERVER HELLO... comment, after the limit_req line: # CVE-2026-111497 interim workaround: reject Brotli request bodies
# before they reach the UI server (localhost:7500). See map above.
if ($reject_br) {
return 415;
}Sample result after the edit (Note: Command used less -N /etc/nginx/nginx.conf):
nginx -t && systemctl reload nginxSample result:
nginx -t fails, restore the configuration from the backup using below steps and contact Global Support:cp -p /root/nginx.conf.before-cve111497 /etc/nginx/nginx.conf
nginx -tnginx cannot see requests sent straight to 127.0.0.1:7500. This step closes that gap.
$APP (/opt/vmware/vcf/sddc-manager-ui-app/server/src/servers/sddcManagerServer/app.js).app.use(bodyParser.json({... call: // CVE-2026-111497: reject Brotli request bodies before any parser runs.
// Other encodings (gzip, deflate) are left as they are.
app.use((req, res, next) => {
if (/\bbr\b/i.test(req.headers['content-encoding'] || '')) {
return res.status(415).json({ message: 'Brotli request bodies are not accepted', status: 415 });
}
next();
});
Sample result after the edit:
systemctl restart sddc-manager-ui-appfor i in $(seq 1 40); do
c=$(curl -s -o /dev/null -w '%{http_code}' -X POST http://127.0.0.1:7500/ui/api/ping \
-H 'Content-Type: application/json' --data-binary '{"a":1}')
[ "$c" != 503 ] && [ "$c" != 000 ] && break
sleep 6
done
echo "ui_code=$c"| Test | Command | Expected after the fix |
| Brotli body, direct to UI | curl -s -o /dev/null -w '%{http_code}' -X POST http://127.0.0.1:7500/ui/api/ping -H 'Content-Type: application/json' -H 'Content-Encoding: br' --data-binary '{"a":1}' | 415 |
| Brotli body, through nginx | same command with -k https://127.0.0.1/ui/api/ping | 415 |
| Plain JSON, through nginx | same command without Content-Encoding | not 415 (normal response, e.g. 401 or 403 if not logged in) |
| gzip body | same command with Command: | not 415 |
nginx -T 2>/dev/null | grep -c reject_br # expect 2 (map + if)
grep -c 'CVE-2026-111497' $APP # expect 1Execute the following commands to revert the files from the backup.
/var/log/vmware/vcf/cve-2026-111497-inbound.log. Attach it to any support request./var/backups/cve-2026-111497/<date-time>/check. An upgrade to a release that includes the fix doesn't need the workaround.