Eclipse OpenMQ: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-24457 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in Eclipse OpenMQ from Eclipse Foundation, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 6.5.2, 6.9.0 as the first without the flaw, so updating Eclipse OpenMQ to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.7% chance of exploitation within 30 days, higher than 54% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Eclipse OpenMQ to 6.5.2 or 6.9.0, whichever matches your release line, or a later version.
- Update Eclipse GlassFish to 7.0.26 or 7.1.1 or 8.0.2, whichever matches your release line, or a later version.
- Read the advisory on gitlab.eclipse.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Eclipse Foundation | Eclipse OpenMQ | before 6.5.2; 6.6.0 up to, but not including, 6.9.0 | 6.5.2, 6.9.0 |
| Eclipse Foundation | Eclipse GlassFish | before 7.0.26; 7.1.0 up to, but not including, 7.1.1; 8.0.0 up to, but not including, 8.0.2 | 7.0.26, 7.1.1, 8.0.2 |
| Eclipse | Openmq | 6.5.1 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | CNA (eclipse.org) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
An unsafe parsing of OpenMQ's configuration in OpenMQ versions <6.5.2 and <6.9.0, 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. This is fixed in OpenMQ 6.5.2, 6.9.0, and in GlassFish 7.0.26, 7.1.1, and 8.0.2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Eclipse OpenMQ
- 9.8 Critical severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.1 High severity
- 9.1 Critical severity
- 7.9 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.