Artica Wiki

CVE-2026-123007 and CVE-2026-123633: nginx HTTP/2 flaws (NGINX2Root)

Two memory safety flaws in the nginx HTTP/2 module: impact on the Artica Web Console and reverse-proxy, and how to disable HTTP/2 until fixed packages are installed.

Status on November 19, 2026: nginx 1.31.9 and 1.30.7 fix both flaws.
No OpenResty release based on a fixed nginx is available yet.
This page will be updated when fixed Artica packages are published.

Summary

CVE-2026-123007 and CVE-2026-123633 are two memory safety flaws in the HTTP/2 module of nginx.
They are also known as "NGINX2Root".

CVE Flaw nginx severity Vulnerable versions Fixed versions
CVE-2026-123007 Memory corruption in HTTP/2 flow control Major 1.9.5 to 1.31.8 1.31.9 and later, 1.30.7 and later
CVE-2026-123633 Use-after-free in HTTP/2 Medium 1.19.7 to 1.31.8 1.31.9 and later, 1.30.7 and later

Both flaws can only be reached over an HTTP/2 connection.
A server that does not offer HTTP/2 is not exposed to them.

How Artica is affected

Two Artica components use nginx.

Component Engine HTTP/2 by default Exposed when
Web Console nginx built by Artica Disabled Use HTTP2 is enabled in the Web Console settings.
Reverse-proxy nginx built by Artica Disabled HTTP/2 is enabled on at least one HTTPS port of a website.

Current Artica packages ship a vulnerable nginx version in both components.
An appliance where HTTP/2 was never enabled is not exposed to these two flaws.

Where HTTP/2 is enabled, the flaws are critical.
On an Artica appliance, the nginx worker processes share their system account with the Web Console.
A successful attack could lead to full control of the appliance.

No public exploit was known when this page was written.

Check if HTTP/2 is enabled

Web Console

Open Your system > Web Console.
In the HTTP service card, look at the HTTP2 line.
On means the console is exposed.

From a shell on the appliance, you can also run:

grep -n http2 /etc/artica-postfix/webconsole.conf

No output means HTTP/2 is disabled.

Reverse-proxy

Open each website of the reverse-proxy, then its Ports tab.
An HTTPS port that shows the HTTP/2 badge is exposed.

The option applies to every HTTPS port of a website.
If one port enables it, the other HTTPS ports of the same website show "Already enabled by another HTTPS port of this website".

From a shell on the appliance, you can also run:

grep -rln "http2 on" /etc/nginx/

Each file listed belongs to a website that offers HTTP/2.

Workaround: disable HTTP/2

Disabling HTTP/2 makes the vulnerable code unreachable.
Browsers switch to HTTP/1.1 automatically.
There is no service interruption.
Pages with many resources may load a little slower.

Web Console

  1. Open Your system > Web Console.
  2. Click the HTTP2 line of the HTTP service card.
  3. Uncheck use HTTP2.
  4. Click apply.

The console restarts its web service.
Reload the page after a few seconds.

Reverse-proxy

For each website where HTTP/2 is enabled:

  1. Open the website, then its Ports tab.
  2. Open each HTTPS port that has HTTP/2 enabled.
  3. Turn off the HTTP/2 switch.
  4. Save.

The website is reloaded when the port is saved.
Repeat for every HTTPS port that has it.
A single enabled port is enough to keep HTTP/2 on for the whole website.

Then run the check again:

grep -rln "http2 on" /etc/nginx/

The command must return nothing.

Fix

Web Console

Artica have published a Web Console package built on nginx 1.31.9 or later.
After installing it, you can enable HTTP/2 again if you need it.

To display the version of the console engine:

/usr/local/ArticaWebConsole/sbin/artica-webconsole -v

Reverse-proxy

The reverse-proxy is updated with 1.31.9.1 based on nginx 1.31.9 or later.
Keep HTTP/2 disabled until then.

To display the version of the reverse-proxy engine:

/usr/sbin/nginx -v

Other nginx flaws fixed by the same update

The nginx 1.31.9 and 1.30.7 releases also fix other 2026 flaws.
One of them applies even without HTTP/2:

Only the package update protects against this flaw.

References