Heads up: nginx security update (CVE-2026-123007 and CVE-2026-123633) - what FileMaker Server on Linux needs to do

  • Wednesday, 18th November, 2026
  • 17:04pm

If your FileMaker Server runs on Linux, it most likely uses nginx as its web server for WebDirect and the Admin Console. An nginx update released on 2026-11-18 is worth your attention.

Hosted with ODITech? You don't need to do anything. Our team will apply the update or mitigation to ODITech-hosted servers that need it. The rest of this article is for people who run their own FileMaker Server.

What it is

Two flaws in nginx's HTTP/2 handling were disclosed this week, and the nginx project released fixed versions 1.30.7 (stable) and 1.31.9 (mainline).

  • CVE-2026-123007: memory corruption in HTTP/2 flow control. Security researchers list all official releases from nginx 1.9.5 through 1.31.8 as affected.
  • CVE-2026-123633: a use-after-free in HTTP/2 connection handling. It applies to HTTP/2 with requests forwarded to an upstream server, from nginx 1.19.7.

Severity is not settled. Wiz Research, which reported them, rates both Critical (CVSS 4.0 9.2) and says it confirmed remote code execution for CVE-2026-123633 in its own testing. nginx.org's own labels are lower ("major" and "medium"), and its fix descriptions do not mention code execution. Treat this as serious until the picture settles. nginx.org lists the full set of fixes, with affected version ranges: https://nginx.org/en/security_advisories.html.

Where your nginx comes from

FileMaker Server (latest build) Installer ships the nginx update script? Default nginx source
19.6.4, 20.3.4 No Ubuntu's own nginx package
21.1.8, 22.0.7 Yes. You run it yourself. Ubuntu's package until the script has been run; nginx.org's after
26.0.3 No (the package depends on the system nginx package) Ubuntu's package, unless the nginx.org repository was added earlier

Which source you are on matters more than your FileMaker version. A server upgraded from 21 or 22 to 26 can still be on nginx.org, while a clean 26.0.3 install is on Ubuntu's package. Updating FileMaker Server does not by itself change where nginx comes from.

Ubuntu's status: as of 2026-11-18, Ubuntu's security tracker listed nginx on 20.04, 22.04 and 24.04 with no fixed package yet. Ubuntu's version numbers (1.18.0 on 20.04 and 22.04, 1.24.0 on 24.04) are not comparable to nginx.org's, so do not assume an old number is safe. Check Ubuntu's tracker again before you act.

FileMaker Server 21 and 22: is the nginx repository set up?

On 21 and 22 the nginx update script is a manual step, and nothing forces it. Check each server:

ls -l /etc/apt/sources.list.d/nginx.list /etc/apt/preferences.d/99nginx
grep -rl 'nginx.org' /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null
apt-cache policy nginx

If both files are missing and the grep prints nothing, the nginx.org repository is not configured and the server gets nginx from Ubuntu.

To set it up, run NginxUpdate.sh from the root of the unarchived FileMaker Server installer folder (the download for the version you run, so you may need to download it again). Take a snapshot and a copy of /opt/FileMaker/FileMaker Server/NginxServer/conf/ first, then run, as root in a terminal:

sudo ./NginxUpdate.sh

The script installs a few prerequisites, adds nginx.org's signing key and apt source for your Ubuntu release, writes a pin file so nginx.org's build is preferred over Ubuntu's, runs apt update and then apt install nginx. Read what apt install nginx proposes before you confirm, and do not accept removal of anything that is not an nginx package.

What to do

  1. Check what you are running. The version in memory is the one that counts:
    sudo /proc/$(pgrep -f 'nginx: master' | head -1)/exe -v
    dpkg-query -W -f='${Version}\n' nginx
    A version ending in ~jammy, ~noble or similar is from nginx.org. Do not run nginx -t or nginx -T on a FileMaker Server box; with FileMaker's configuration they can hang.
  2. Snapshot or back up first, and copy /opt/FileMaker/FileMaker Server/NginxServer/conf/. An nginx package upgrade has been known to overwrite FileMaker's custom nginx configuration.
  3. Upgrade the package:
    sudo apt update
    sudo apt install nginx
    Read the list apt proposes and accept only nginx-related changes. Never apt purge nginx: FileMaker Server depends on it. If apt offers nothing newer, the fix is not available from your source yet.
  4. Restart the web tier so the new binary actually runs. FileMaker starts nginx through its own services, so installing the package alone can leave the old process running:
    fmsadmin restart httpserver
    It asks for confirmation and admin credentials. Then re-run the version check from step 1.
  5. Re-check your configuration (SSL, custom blocks, any hardening you applied), because the upgrade can replace config files.
  6. Target versions: 1.30.7 or later on stable, 1.31.9 or later on mainline.

If you can't patch right away

Both researchers say disabling HTTP/2 on the affected listeners blocks both flaws. On FileMaker Server that means editing FileMaker's managed nginx configuration. We have not tested it, and FileMaker updates may overwrite the change, so treat it as a last resort.

Ubuntu 20.04 is the hard case. nginx.org's builds for 20.04 stop at 1.28.0, which has no fix listed. The options are Ubuntu Pro or an operating system upgrade (which may need a newer FileMaker Server; check Claris's supported-OS list).

Quick checklist

  • ☐ Know whether each server's nginx comes from Ubuntu or nginx.org
  • ☐ Check the running version, not just the installed one
  • ☐ Snapshot and copy the nginx configuration
  • ☐ Upgrade the package and run fmsadmin restart httpserver
  • ☐ Confirm 1.30.7 / 1.31.9 or later, then re-check your configuration

Questions, or want us to patch your server? Email us at support@oditech.com

Sources: nginx security advisories, Wiz Research, Xint.

« Back