⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.2

How to Fix CVE-2026-22542: Denial of Service in QC 60/90/120

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.2 - Critical
Actively exploited?Not currently listed in CISA KEV
Affected8
Fixed inSee vendor advisory
Type (CWE)CWE-400: Uncontrolled Resource Consumption

What is CVE-2026-22542?

CVE-2026-22542 is a denial of service flaw in QC 60/90/120. A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor description: An attacker with access to the system's internal network can cause a denial of service on the system by making two concurrent connections through the Telnet service.

Why this CVE matters

Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.

For deployments of QC 60/90/120 that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open QC 60/90/120's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-22542

  1. Read the vendor advisory in full: https://cds.thalesgroup.com/en
  2. Upgrade QC 60/90/120 to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Ubuntu / Debian

_Verify the exact patched build against the vendor advisory: https://cds.thalesgroup.com/en_


sudo apt-get update
sudo apt-get install --only-upgrade qc6090120
dpkg -s qc6090120 | grep -i version

RHEL / Rocky / AlmaLinux / Fedora


sudo dnf upgrade --refresh qc6090120 -y
rpm -q qc6090120

openSUSE


sudo zypper refresh
sudo zypper update qc6090120
rpm -q qc6090120

Bash detect / upgrade / verify runner (Linux)

_Verify the exact patched build against the vendor advisory: https://cds.thalesgroup.com/en_


#!/usr/bin/env bash
# CVE-2026-22542 remediation runner. Re-runnable; exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-22542-fix.log; }

PKG="qc6090120"
TARGET_VERSION="see vendor advisory"

log "Detect: reading current $PKG version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' "$PKG" 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' "$PKG" 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current (target per advisory: $TARGET_VERSION)"

log "Backup: snapshotting /etc/$PKG if present"
backup="/var/backups/cve-2026-22542-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d "/etc/$PKG" ] && cp -a "/etc/$PKG" "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade "$PKG"
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y "$PKG"
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y "$PKG"
fi

log "Verify: re-reading $PKG version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' "$PKG")
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' "$PKG")
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: $PKG upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

Verify the fix landed


# 1. Confirm the running version matches the patched build
#    (target per advisory: see vendor advisory)
#    Use the platform-specific version probe shown above.

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    Rapid7, OpenVAS). The scanner should no longer flag CVE-2026-22542.

# 3. Inspect service and kernel logs for crash-loops or rollback events
journalctl --since "10 minutes ago" | grep -iE 'error|fail|panic'
dmesg --since "10 minutes ago" | tail -50

If you cannot patch immediately

Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-22542 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-22542?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for QC 60/90/120 run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*