Veeam nginx flaws: restrict appliance access while fixes are pending

Conceptual backup appliance inside a cyan network boundary, with amber incoming connections stopped at a gateway.

Your backup appliance needs a network-exposure check while a fix is pending. Veeam’s new KB4976, published and last modified November 20, 2026, identifies different nginx remediation paths across its appliances and backup services. Match the actual component before changing anything.

The advisory covers CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425. Veeam describes remotely triggerable memory-corruption flaws in HTTP/2, HTTP/3, DNS-resolver and mail-proxy features. Applicability depends on both the nginx build and enabled features. Its statement says a chain with a Linux kernel vulnerability can lead to root access, but does not identify that kernel CVE or establish root compromise of every deployment.

Apply the product-specific path

ProductApplicabilityVendor action
Software Appliance 13.1 / Infrastructure Appliance 13.1Affected nginx with HTTP/2 enabled. No fixed package yet.Restrict TCP 443 to trusted networks. Do not disable HTTP/2: Veeam components require it. Track the fix through Veeam Updater.
AWS / Google Cloud / Microsoft Azure plug-in appliancesAffected until nginx is updated; appliances use Ubuntu 22.04 LTS.Install all available security updates through Veeam Updater. Veeam identifies nginx 1.18.0-6ubuntu14.23 as patched. Cloud-appliance product version bounds are not supplied.
Backup for Salesforce 3.2.1CVE-2026-123007 and CVE-2026-123633 apply to its HTTP/2 backend-proxy configuration.Apply the OS vendor’s nginx update or use Veeam’s HTTP/2-disable procedure. The other three CVEs do not apply to this configuration.
Data Cloud for Salesforce / Microsoft Azure / AWSVeeam remediation is in progress.No customer action required; this is not a statement that remediation is complete.
Backup Enterprise Manager on Linux 13.1 / hypervisor plug-in workersNot affected under the configurations described by Veeam.No action required for this issue. Public-cloud worker instances do not include nginx and are also excluded.

Salesforce workaround has a narrow scope

For customer-managed Veeam Backup for Salesforce 3.2.1, Veeam directs administrators to edit /etc/nginx/sites-available/vbsf-frontend.conf, change listen 443 ssl http2; to listen 443 ssl;, save, validate with sudo nginx -t, then restart nginx.service. Follow the full KB and validate application operation. This procedure must not be transferred to Software Appliance or Infrastructure Appliance 13.1, where Veeam says HTTP/2 cannot be disabled.

Priority and exploitation facts

Suggested MSP priority: high for confirmed affected backup infrastructure; contain promptly if TCP 443 is reachable from untrusted networks. This is an operational recommendation. KB4976 supplies no vendor severity label, numeric CVSS, complete older affected-version bounds or confirmed malicious-exploitation statement. The five CVEs are absent from the full CISA KEV catalog checked November 20; there is no corresponding KEV federal deadline. Public vulnerability information is not proof of an attack against Veeam. No blanket compromise-check or credential-rotation requirement is supplied in this KB.

Inventory → contain → update → verify

Inventory the actual Veeam component, appliance/build, nginx package, HTTP/2 configuration and TCP 443 reachability across customer environments. For the two affected 13.1 appliances, restrict access to trusted networks while preserving required backup and management paths. Use the supported Veeam Updater path when a fix is released; cloud plug-in appliances already have a vendor-identified patched Ubuntu package. For Salesforce, use its own OS update or documented workaround. Verify the loaded package and running nginx service, effective network restrictions, management access, completed backup jobs and an appropriate restore test. Package availability alone does not establish an installed fix. Treat suspicious activity through the existing incident-response process.

Official evidence and limits

Veeam KB4976: NGINX2ROOT Impact Statement · Veeam official security-only feed · Veeam appliance update guidance · Public-cloud appliance update guidance · CISA KEV.

Last verified November 20, 2026 against the accessible vendor KB and matching full entry in Veeam’s official security feed. No customer deployment is assumed. Other Veeam products, versions and unrelated Microsoft 365 backup components are not cleared by this table; keep unlisted applicability with the vendor.

Share this article