nginx HTTP/2 vulnerabilities (CVE-2026-123633, CVE-2026-123007): impact on SFTP Gateway
TLDR - Quick Summary
What: On November 18, 2026, two vulnerabilities were published in nginx, the web server in front of the SFTP Gateway web admin interface: CVE-2026-123633 and CVE-2026-123007. Both are in nginx's HTTP/2 support, which is turned on in our images. The flaws are in nginx itself, not in SFTP Gateway code. SFTP is not involved.
Affected: SFTP Gateway 3.0.0 through 3.10.0, on every cloud and in containers.
Action: Update nginx from your operating system's packages and restart nginx (Step 1). Fixed packages are available for Amazon Linux 2023, Amazon Linux 2 and Ubuntu. If you cannot update yet, turn off HTTP/2 instead. For containers, restrict access to the web admin port until SFTP Gateway 3.10.1. No exploitation has been reported.
Last updated: 2026-11-19.
Summary
No exploitation of these issues has been reported. As of November 18, 2026, there were no public reports of them being used in real attacks. A proof-of-concept for CVE-2026-123007 was published the same day; its authors describe it as suitable only for a lab demonstration. Both vulnerabilities carry a CVSS 4.0 score of 9.2 (Critical); Ubuntu and Amazon Linux rate them 8.1 (High) under CVSS 3.1. Because the affected code can be reached without logging in, we recommend updating now.
Affected versions
SFTP Gateway 3.0.0 through 3.10.0. The web admin interface of these versions answers over HTTP/2.
The fix also ships in SFTP Gateway 3.10.1, our next patch release, currently planned for early December. You do not need to wait for it: updating nginx on your server (Step 1) fixes the issue today.
Which servers are exposed
A server is exposed until its nginx package is updated to a fixed version (Step 1), unless HTTP/2 has been turned off. This does not depend on the processor or instance type.
What the risk is
The affected nginx code can be reached through the web admin interface over HTTPS (port 443) before login. The SFTP port is not involved, because nginx does not handle SFTP. In the worst case described by the researchers who found the flaws, an attacker could run code on the server. An attack that only crashes nginx would interrupt the web admin interface; SFTP keeps running.
If your web admin interface is open to the internet, restricting it to trusted IP addresses reduces your exposure right away.
Step 1: Update nginx
These steps are written for a single server. If you run high availability or a custom build, apply the same update to each server.
Fixed versions
| Operating system | Where | Fixed nginx package | Vendor advisory |
|---|---|---|---|
| Amazon Linux 2023 | AWS | 1.30.7-1.amzn2023.0.1 | ALAS2023-2026-3494 |
| Amazon Linux 2 | AWS, older images | 1.30.7-1.amzn2.0.1 | ALAS2NGINX1-2026-018 |
| Ubuntu 24.04 | Azure and Google Cloud | 1.24.0-2ubuntu7.20 | USN-9159-1 |
| Ubuntu 22.04 | Azure and Google Cloud, older images | 1.18.0-6ubuntu14.23 | USN-9159-1 |
To see which operating system your server runs:
grep PRETTY_NAME /etc/os-release
Restarting nginx interrupts the web admin interface for less than a second. It does not disconnect SFTP sessions.
The update does not change your SFTP Gateway configuration. website.conf is not part of the nginx package, so it is left as it is. If you have edited nginx.conf, your copy is kept; on Amazon Linux, the new default is saved next to it as nginx.conf.rpmnew. On servers built from older Amazon Linux 2023 images, the update also installs newer OpenSSL and OpenSSH packages along with nginx; your SSH settings, including the port OpenSSH listens on, are kept.
Amazon Linux 2023
sudo dnf --releasever=latest update nginx
sudo systemctl restart nginx
The --releasever=latest option is needed because Amazon Linux 2023 installs packages only from the release your server was built on, which does not include the fix. It applies to this command only and does not change the release your server follows.
Amazon Linux 2
sudo yum update nginx
sudo systemctl restart nginx
Amazon Linux 2 installs security updates on a server's first boot, so a server launched recently may have the fix already. In that case the command reports No packages marked for update.
Ubuntu (Azure, Google Cloud)
Our Ubuntu images install security updates automatically once a day, so most servers already have the fixed package, and the update restarts nginx on its own. To check, or to install it right away:
sudo apt-get update
sudo apt-get install --only-upgrade nginx
sudo systemctl restart nginx
Confirm the update
Check the installed version against the table above.
Amazon Linux:
rpm -q nginx
Ubuntu:
dpkg-query -W nginx
zgrep -c CVE-2026-123007 /usr/share/doc/nginx/changelog.Debian.gz
On Ubuntu, the second command prints 0 until the fixed package is installed.
Containers (Docker, Kubernetes, Helm)
There is no fixed container image yet. nginx is part of the web admin interface image, so it cannot be updated inside a running container. The fix ships in the SFTP Gateway 3.10.1 container images. Until then, restrict access to the web admin container's HTTPS port to trusted IP addresses.
Helm: list the trusted addresses under
ui.service.loadBalancerSourceRangesin your values file, then runhelm upgradeas you normally do.ui: service: loadBalancerSourceRanges: - "203.0.113.50/32"Docker, Docker Compose and other Kubernetes deployments: restrict the published HTTPS port with your firewall, security group or network policy.
If a load balancer or ingress terminates TLS in front of the container, and the container runs with EXTERNAL_TLS_TERMINATION=true (SFTP Gateway 3.9.0 and later), the container serves plain HTTP/1.1 only and is not exposed.
To check a container, run this from a machine that can reach its HTTPS port. 2 means exposed, 1.1 means HTTP/2 is off:
curl -sk --http2 -o /dev/null -w '%{http_version}\n' https://<host>:<https-port>/
If you cannot update nginx yet
Turning off HTTP/2 in nginx protects a server until you can update it. The web admin interface keeps working over HTTP/1.1.
To check whether HTTP/2 is on, run:
curl -sk --http2 -o /dev/null -w '%{http_version}\n' https://localhost/
If the command prints 2, HTTP/2 is on. If it prints 1.1, HTTP/2 is off.
Run the command for your platform. Copy and paste it rather than typing it. It is safe to run more than once.
AWS (Amazon Linux):
sudo sed -i 's/ ssl http2;/ ssl;/' /etc/nginx/conf.d/website.confAzure and Google Cloud (Ubuntu):
sudo sed -i 's/ ssl http2;/ ssl;/' /etc/nginx/sites-available/website.confCheck the configuration and restart nginx. This interrupts the web admin interface for less than a second. It does not disconnect SFTP sessions.
sudo nginx -t && sudo systemctl restart nginxConfirm HTTP/2 is off. This should now print
1.1:curl -sk --http2 -o /dev/null -w '%{http_version}\n' https://localhost/
The change stays in place after a reboot and after operating system updates.
After an in-place product upgrade: the upgrade installs a new copy of the nginx configuration file with HTTP/2 turned on. If nginx has not been updated yet, repeat these steps after upgrading.
New servers: a server launched from a current image has HTTP/2 turned on. Update nginx on it (Step 1), or repeat these steps.
Once nginx is updated, HTTP/2 can be turned back on by reversing these steps. It is also safe to leave it off.
Other nginx CVEs published the same day
The nginx release that fixes these two issues also fixes several others, and security scanners may list them against the nginx package: CVE-2026-118899, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425, CVE-2026-125283, CVE-2026-120967 and CVE-2026-123640. On container images, which use a newer nginx line, scanners may also list CVE-2026-120993. These need features that the SFTP Gateway web admin configuration does not use (the resolver, HTTP/3, the mail proxy, the stream module, the PROXY protocol, or alias), or TLS 1.3, which the SFTP Gateway web admin interface does not accept.
On Amazon Linux, the update in Step 1 fixes all of them. On Ubuntu, it fixes all of them except CVE-2026-125283, which Ubuntu has not released a fix for yet. That one needs the alias directive, so it cannot be reached on SFTP Gateway, but scanners may keep listing it on Ubuntu until Ubuntu releases a fix.
References
nginx security advisories: https://nginx.org/en/security_advisories.html
Amazon Linux 2023 advisory ALAS2023-2026-3494: https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3494.html
Amazon Linux 2 advisory ALAS2NGINX1-2026-018: https://alas.aws.amazon.com/AL2/ALAS2NGINX1-2026-018.html
Ubuntu security notice USN-9159-1: https://ubuntu.com/security/notices/USN-9159-1
Amazon Linux security center: https://explore.alas.aws.amazon.com/CVE-2026-123007.html and https://explore.alas.aws.amazon.com/CVE-2026-123633.html
Ubuntu security tracker: https://ubuntu.com/security/CVE-2026-123007 and https://ubuntu.com/security/CVE-2026-123633
Wiz research: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities