● Critical · CVSS 9.1

How to Fix CVE-2026-24457: Path traversal in Eclipse OpenMQ

Q: What is the CVSS score for CVE-2026-24457?

9.1 (Critical). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`.

Q: Where is the official advisory for CVE-2026-24457?

The vendor advisory is at [https://gitlab.eclipse.org/security/cve-assignment/-/issues/84](https://gitlab.eclipse.org/security/cve-assignment/-/issues/84). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-24457.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-24457 is a path traversal in Eclipse Foundation Eclipse OpenMQ. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	9.1 (Critical)
Actively exploited?	No public listing in CISA KEV
Affected	Eclipse OpenMQ 0 to <=6.5.1
Fixed in	See vendor advisory
Type (CWE)	CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-24457?

An unsafe parsing of OpenMQ's configuration, allows a remote attacker to read arbitrary files from a MQ Broker's server. A full exploitation could read unauthorized files of the OpenMQ’s host OS. In some scenarios RCE could be achieved. The CVSS base score is 9.1 (Critical), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://gitlab.eclipse.org/security/cve-assignment/-/issues/84.

Am I affected?

Check the version of Eclipse OpenMQ you are running and compare it against the Affected row above (Eclipse OpenMQ 0 to <=6.5.1). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s eclipse-openmq 2>/dev/null | grep -i ^Version
rpm -q eclipse-openmq 2>/dev/null
command -v eclipse-openmq >/dev/null && eclipse-openmq --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Eclipse OpenMQ*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Eclipse OpenMQ" 2>$null

How to fix CVE-2026-24457

Upgrade Eclipse OpenMQ to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade eclipse-openmq
dpkg -s eclipse-openmq | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh eclipse-openmq -y
# or for older releases:
sudo yum update eclipse-openmq -y
rpm -q eclipse-openmq

SUSE / openSUSE


sudo zypper refresh
sudo zypper update eclipse-openmq
rpm -q eclipse-openmq

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-24457 affecting Eclipse OpenMQ
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-24457-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Eclipse OpenMQ*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\eclipse-openmq-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Eclipse OpenMQ" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Eclipse OpenMQ" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Eclipse OpenMQ"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-24457 affecting Eclipse OpenMQ
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-24457-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s eclipse-openmq 2>/dev/null | grep -i ^Version || echo "eclipse-openmq not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q eclipse-openmq || echo "eclipse-openmq not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-24457-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/eclipse-openmq /etc/eclipse-openmq.d /etc/eclipse-openmq.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y eclipse-openmq
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y eclipse-openmq
elif command -v yum >/dev/null; then
    yum update -y eclipse-openmq
elif command -v zypper >/dev/null; then
    zypper --non-interactive update eclipse-openmq
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s eclipse-openmq 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q eclipse-openmq
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-24457" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-24457"

Disable the affected service (Linux)


sudo systemctl stop eclipse-openmq 2>/dev/null || true
sudo systemctl disable eclipse-openmq 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s eclipse-openmq 2>/dev/null | grep -i ^Version
rpm -q eclipse-openmq 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Eclipse OpenMQ*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

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

How to Fix CVE-2026-7672: SQL Injection in youlai-boot — SQL Injection in youlai-boot
How to Fix CVE-2026-32427: Missing Authorization in VW Education Lite — Missing Authorization in VW Education Lite
How to Fix CVE-2026-7098: Buffer Overflow in F456 , Buffer Overflow in F456
How to Fix CVE-2026-35454: Code Extension Marketplace has a Zip Slip Path Traversal , Code Extension Marketplace has a Zip Slip Path Traversal
How to Fix CVE-2026-1459: Os command injection in VMG3625-T50B firmware , Os command injection in VMG3625-T50B firmware

Is CVE-2026-24457 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-24457?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-24457?

9.1 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H.

Where is the official advisory for CVE-2026-24457?

The vendor advisory is at https://gitlab.eclipse.org/security/cve-assignment/-/issues/84. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-24457.

References

Official vendor advisory: https://gitlab.eclipse.org/security/cve-assignment/-/issues/84
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24457
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*