This morning we learned about a new vulnerability in the Java Virtual Machine, CVE-2026-114938, popularly known as “Java4Shell”. It may affect some QueueMetrics systems.

You do not need to worry. At the time of writing, no active exploits of this vulnerability have been reported, and protecting your system takes only a few minutes. Updated Java packages are not available yet, so for now you need to make one small change to your configuration.

Who is affected

Only systems that run QueueMetrics 26.10 may be affected. This applies both to systems installed directly on the operating system and to systems that run on Docker.

Systems based on older QueueMetrics releases, and WombatDialer, still use Java 8. They are not affected by this vulnerability.

If you run an older QueueMetrics, you still need to upgrade. New security issues will come out, and when they do, you must be able to fix them quickly. As we wrote about PHP2Shell, no product is immune, so you need to be prepared. Our tutorial How to upgrade QueueMetrics by migrating to a new server shows you how.

Why QueueMetrics 26.10 is affected

The problem is in the way the Java virtual machine decodes content in Base64 format. Any software that communicates over the web, either as a server or as a client that sends requests, may be exposed.

At the time of writing, the operating systems have not yet released Java versions later than 25.0.5. Until they do, the Java virtual machines on these systems are vulnerable.

The problem only exists on x86-64 (amd64) machines whose processors have the AVX-512 VBMI extensions. These are Intel Xeon processors from the Ice Lake generation onward, and AMD processors from Zen 4 onward. ARM systems are not affected.

The change below protects your system while you wait for the updated Java packages.

What to do on a local installation

Step 1 - Check your architecture

If you are not sure which architecture your system uses, open QueueMetrics and go to Home → View Configuration → JVM Properties. Look at the value of os.arch.

If the value is amd64, your system may be affected. Even if you do not know which extensions your processor has, we recommend that you make the change below. Its CPU cost is negligible, so it is worth doing in any case.

Step 2 - Add the parameter

Edit the file /etc/default/queuemetrics:

vi /etc/default/queuemetrics

Add the parameter -XX:-UseBASE64Intrinsics to QM_JAVA_OPTS. Do not change the other parameters. The result looks like this:

QM_JAVA_OPTS="
                -server -XX:-UseBASE64Intrinsics   \
                -Djava.security.egd=file:/dev/./urandom \
                -XX:+UseG1GC -XX:MaxGCPauseMillis=500 -XX:InitiatingHeapOccupancyPercent=45 \
                -Djava.net.preferIPv4Stack=true \
                -Djdk.tls.ephemeralDHKeySize=2048 \
                -Dtomcat.instance=loway
"

Step 3 - Restart and check

Restart QueueMetrics:

queuemetrics-cli restart

Then check that it started again:

queuemetrics-cli status | grep Active:

You should see a line like this one:

     Active: active (running) since Wed 2026-11-18 08:09:29 UTC; 45s ago

That’s it: your system is protected.

What to do on Docker

If you run QueueMetrics on Docker, we will release QueueMetrics 26.10.7 later today on our Docker Hub page. This new version contains the parameter. When it is available, update your container.

First, download the new image:

docker pull loway/queuemetrics:latest

Then stop and delete the old container. Your data is kept, as long as the container stores it in a data folder or a data volume:

docker stop QM1
docker rm QM1

Finally, start the container again with the same data folder:

docker run --name=QM1 --volume=/opt/qm1data:/data -P -d loway/queuemetrics

Replace QM1 and /opt/qm1data with the container name and the data folder that you use. Also add any other options that you used when you first started the container, for example -p or -e CFG=.... For more details, see Docker for QueueMetrics.

What comes next

When the operating systems release updated Java packages, you will need to update Java. Update it with the package manager of your distribution, then restart QueueMetrics with queuemetrics-cli restart. After you update Java, you can remove the -XX:-UseBASE64Intrinsics parameter, or leave it in place.

We will update this page in the coming days.

Clients on QueueMetrics Live do not need to do anything, as the problem has already been fixed there.

About QueueMetrics

QueueMetrics is a highly scalable monitoring software that lets you track agent productivity, payrolls, measure targets, conversion rates, queues/ACDs, IVRs, music-on-hold, generate outbound campaign statistics and monitor realtime processes with customizable wallboards.

You can measure all activities in your contact center with more than 200 different metrics and manage realtime processes with live alarms and full control on calls and extensions, including whisper, spy and barge modes.

QueueMetrics is available on premise or as a cloud hosted service, and it is compatible with FreePBX, Grandstream, Issabel, MiRTA, Enswitch, Yeastar S PBX, VitalPBX, FusionPBX and many other Asterisk- and Freeswitch-based systems. It also supports Microsoft Teams telephony.

For more technical information please refer to the User Manual.

Visit www.queuemetrics.com for a free 15-day full-featured trial.

keyboard_arrow_left Back