Quick answers
- Is CVE-2026-24457 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24457 being exploited in the wild.
- How severe is CVE-2026-24457?
- Critical severity, with a CVSS score of 9.1, published 5 March 2026.
- Which products and versions are affected?
- Eclipse Openmq <6.5.2 and <6.9.0.
- Is there a fix for CVE-2026-24457?
- A patch was published on 2026: Patches released in OpenMQ 6.5.2, 6.9.0 and GlassFish 7.0.26, 7.1.1, 8.0.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24457 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-24457?
- Check whether you run Eclipse Openmq at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability stems from unsafe parsing of OpenMQ's configuration files, enabling a path traversal or similar file disclosure attack (CWE-22, CWE-27). The vulnerability is remotely exploitable from the network without requiring authentication or special preconditions. An attacker can leverage the misconfigured parser to read unauthorized files on the OpenMQ broker's filesystem, including host OS files, and potentially achieve remote code execution in certain scenarios. Patched versions are available: OpenMQ 6.5.2, 6.9.0, and integrated in GlassFish 7.0.26, 7.1.1, and 8.0.2.
Affected products
- Eclipse OpenMQ <6.5.2 and <6.9.0
- Oracle GlassFish <7.0.26, <7.1.1, <8.0.2
- Payara Payara Server versions with bundled OpenMQ <6.5.2 and <6.9.0
Timeline
- 2026-03-05: disclosed: Vulnerability published on NVD
- 2026: patched: Patches released in OpenMQ 6.5.2, 6.9.0 and GlassFish 7.0.26, 7.1.1, 8.0.2