Eine unsichere Verarbeitung von OpenMQ's Konfiguration, ermöglicht einem entfernten Angreifer das Lesen beliebiger Dateien vom MQ Broker Server. Eine vollständige Ausnutzung könnte unautorisierte Dateien des OpenMQ Host OS lesen. In s

The impact of CVE-2026-24457 is significant due to the potential for unauthorized data disclosure and remote code execution. An attacker exploiting this vulnerability can read any file accessible to the OpenMQ process, including configuration files, credentials, and potentially even system files. This could lead to the compromise of the entire OpenMQ broker and potentially the underlying host system. The description explicitly mentions that in some scenarios, RCE (Remote Code Execution) could be achieved, dramatically expanding the attack surface and allowing for complete system takeover. This vulnerability shares similarities with other configuration parsing flaws that have led to RCE in the past.

Organizations utilizing Eclipse OpenMQ as a messaging broker are at risk, particularly those with publicly accessible brokers or those running older, unpatched versions. Shared hosting environments where multiple users share the same OpenMQ instance are also at increased risk, as a compromise of one user's environment could potentially lead to the compromise of others.

• java / server:

find /opt/eclipse/openmq/ -name 'config.xml' -print

• java / server:

ps aux | grep -i openmq

• generic web: Check OpenMQ broker logs for unusual file access attempts. Look for patterns indicating attempts to read files outside of the expected configuration directory. • generic web: Monitor network traffic to the OpenMQ broker for suspicious requests.

1. 2026-03-05Disclosure

   disclosure

1. Reserviert2026-01-23
2. Veröffentlicht2026-03-05
3. Geändert2026-03-06
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2026-24457 is to upgrade to a patched version of Eclipse OpenMQ as soon as it becomes available. Until a patch is applied, consider implementing temporary workarounds to limit the potential impact. These may include restricting network access to the OpenMQ broker, implementing strict file system permissions to limit the files accessible to the OpenMQ process, and carefully reviewing and validating all configuration files. Web Application Firewalls (WAFs) or proxy servers can be configured to filter potentially malicious requests targeting the OpenMQ configuration parsing endpoint. Monitor OpenMQ logs for unusual file access attempts.