Skip to main content
News

NGINX2Root vulnerabilities: update your Universal containers

  • Nov 19, 2026 1:05 PM UTC
  • 4 replies
  • 92 views
Remco Kort
Administrator
Forum|alt.badge.img+3

Security researchers at Xint have disclosed NGINX2Root, a set of vulnerabilities in the nginx web server. They showed that these flaws can take an attacker from an ordinary visitor of a website served by nginx all the way to root access on the server host. The nginx team has fixed them in nginx 1.31.9, as listed in the nginx security advisories.

The vulnerabilities are tracked as:

CVE-2026-123007: memory corruption in HTTP/2 flow control (major)

CVE-2026-123634: use-after-free in the resolver (medium)

CVE-2026-123633: use-after-free in HTTP/2 (medium)

CVE-2026-121810: use-after-free in HTTP/3 (medium)

CVE-2026-113425: use-after-free in the mail proxy module (major)

 

What is affected

This affects our Universal UI containers which use nginx to serve the Universal UI files.

You may also run nginx yourself, for example to host the Universal UI or as a reverse proxy in front of Indicium. In that case, your nginx installation is affected as well.

No other components of the platform are shipped using nginx by default. This includes Indicium itself, the Software Factory, Intelligent Application Manager (IAM), the Windows GUI and your database. A Universal UI hosted on IIS is not affected either.

 

What you need to do

What you need to do depends on how you host the Universal UI.

Thinkwise Cloud: We have updated all Thinkwise Cloud environments. You do not need to take any action.

Universal UI container (self-hosted): We are releasing new versions of the Universal UI container images with an updated nginx version. Pull the new version of the Universal UI image you use and restart your containers.

Your own nginx installation: If you use nginx to host the Universal UI, or as a reverse proxy or load balancer for Indicium, update nginx to version 1.30.7 (stable) or version 1.31.9 (mainline) or later right away.

Your own IIS installation: IIS is not affected, so no action is required.

This vulnerability only applies if you are either using Universal containers or nginx as a webserver (or reverse proxy / load balancer). If you use IIS and the regular Universal package downloaded from TCP,  no further action is required.

 

Our commitment to security

We closely monitor the security of all third-party libraries and components used in our platform. When a vulnerability affects the Thinkwise Platform, we inform you here on the Thinkwise Community.

4 replies

J. de Lange
Hero
Forum|alt.badge.img+4

Which version of the universal GUI do we need to fix this? I only see a nightly build that was recently added.


Remco Kort
Administrator
Forum|alt.badge.img+3
  • Author
  • Administrator
  • Nov 19, 2026 2:25 PM UTC

Which version of the universal GUI do we need to fix this? I only see a nightly build that was recently added.

Are you deploying Universal using Thinkwise provided containers or do you download the Universal UI from TCP? Because this only applies to container version of Universal. The regular download from TCP does not include nginx.


J. de Lange
Hero
Forum|alt.badge.img+4

Which version of the universal GUI do we need to fix this? I only see a nightly build that was recently added.

Are you deploying Universal using Thinkwise provided containers or do you download the Universal UI from TCP? Because this only applies to container version of Universal. The regular download from TCP does not include nginx.

Ah, thank you. We use the regular downloads from the TCP, so I guess we worried over nothing. 


Remco Kort
Administrator
Forum|alt.badge.img+3
  • Author
  • Administrator
  • Nov 19, 2026 2:52 PM UTC

Which version of the universal GUI do we need to fix this? I only see a nightly build that was recently added.

Are you deploying Universal using Thinkwise provided containers or do you download the Universal UI from TCP? Because this only applies to container version of Universal. The regular download from TCP does not include nginx.

Ah, thank you. We use the regular downloads from the TCP, so I guess we worried over nothing. 

I have updated the blogpost to make this clearer. If you are not using Universal containers or Nginx you don’t have to take any further action.