CVE-2026-22886: CWE-1392 Use of Default Credentials in Eclipse Foundation Eclipse OpenMQ
OpenMQ exposes a TCP-based management service (imqbrokerd) that by default requires authentication. However, the product ships with a default administrative account (admin/ admin) and does not enforce a mandatory password change on first use. After the first successful login, the server continues to accept the default password indefinitely without warning or enforcement. In real-world deployments, this service is often left enabled without changing the default credentials. As a result, a remote attacker with access to the service port could authenticate as an administrator and gain full control of the protocol’s administrative features.
AI Analysis
Technical Summary
Eclipse OpenMQ includes a TCP-based management service called imqbrokerd, which is designed to require authentication for administrative access. However, the product ships with a default administrative account using the username 'admin' and password 'admin'. Critically, the software does not enforce or even prompt for a password change upon first login, allowing the default credentials to remain indefinitely valid. This design flaw (CWE-1392) leads to a situation where any remote attacker with network access to the management service port can authenticate as an administrator without needing to guess or brute force credentials. Once authenticated, the attacker gains full control over the broker’s administrative features, potentially allowing them to manipulate messaging queues, intercept or alter messages, disrupt service availability, or pivot to other parts of the network. The vulnerability is rated with a CVSS 3.1 score of 9.8 (critical) due to its network attack vector, no required privileges or user interaction, and complete compromise potential of confidentiality, integrity, and availability. Although no public exploits are currently known, the vulnerability is straightforward to exploit and frequently exposed in real-world deployments where default credentials remain unchanged and the management service is enabled and reachable. The affected versions are indicated as version 0, suggesting early or initial releases of OpenMQ are impacted. The vulnerability is assigned CWE identifiers related to use of default credentials and improper authentication enforcement.
Potential Impact
The impact of CVE-2026-22886 is severe for organizations worldwide using Eclipse OpenMQ, particularly those exposing the management service on networks accessible to attackers. Successful exploitation results in full administrative control over the messaging broker, enabling attackers to intercept, modify, or delete messages, disrupt messaging services, and potentially use the compromised broker as a foothold for lateral movement within the network. This can lead to data breaches, service outages, and loss of trust in critical messaging infrastructure. Industries relying on OpenMQ for asynchronous communication, such as financial services, telecommunications, healthcare, and government, face heightened risk due to the critical nature of message integrity and availability. The vulnerability’s ease of exploitation and lack of required authentication or user interaction increase the likelihood of attacks, especially in environments with weak network segmentation or exposed management interfaces. The absence of mandatory password changes on first use exacerbates the risk, as many deployments may unknowingly operate with default credentials. The overall impact includes potential large-scale disruption of enterprise messaging systems, data compromise, and operational downtime.
Mitigation Recommendations
To mitigate CVE-2026-22886, organizations should immediately audit their Eclipse OpenMQ deployments to identify if the imqbrokerd management service is enabled and accessible over the network. If the service is not required, it should be disabled entirely to eliminate the attack surface. For deployments requiring management access, the default administrative credentials must be changed immediately to a strong, unique password. Since the product does not enforce password changes, manual intervention is necessary. Network-level controls such as firewall rules or VPNs should restrict access to the management service port to trusted administrators only. Additionally, organizations should implement monitoring and alerting for unusual authentication attempts or administrative actions on the broker. Regular vulnerability scanning and configuration reviews should be conducted to ensure no default credentials remain in use. Finally, organizations should track vendor updates and apply patches or configuration changes once available to address this vulnerability at the software level.
Affected Countries
United States, Germany, United Kingdom, France, Japan, South Korea, India, Canada, Australia, Netherlands, Singapore
CVE-2026-22886: CWE-1392 Use of Default Credentials in Eclipse Foundation Eclipse OpenMQ
Description
OpenMQ exposes a TCP-based management service (imqbrokerd) that by default requires authentication. However, the product ships with a default administrative account (admin/ admin) and does not enforce a mandatory password change on first use. After the first successful login, the server continues to accept the default password indefinitely without warning or enforcement. In real-world deployments, this service is often left enabled without changing the default credentials. As a result, a remote attacker with access to the service port could authenticate as an administrator and gain full control of the protocol’s administrative features.
AI-Powered Analysis
Technical Analysis
Eclipse OpenMQ includes a TCP-based management service called imqbrokerd, which is designed to require authentication for administrative access. However, the product ships with a default administrative account using the username 'admin' and password 'admin'. Critically, the software does not enforce or even prompt for a password change upon first login, allowing the default credentials to remain indefinitely valid. This design flaw (CWE-1392) leads to a situation where any remote attacker with network access to the management service port can authenticate as an administrator without needing to guess or brute force credentials. Once authenticated, the attacker gains full control over the broker’s administrative features, potentially allowing them to manipulate messaging queues, intercept or alter messages, disrupt service availability, or pivot to other parts of the network. The vulnerability is rated with a CVSS 3.1 score of 9.8 (critical) due to its network attack vector, no required privileges or user interaction, and complete compromise potential of confidentiality, integrity, and availability. Although no public exploits are currently known, the vulnerability is straightforward to exploit and frequently exposed in real-world deployments where default credentials remain unchanged and the management service is enabled and reachable. The affected versions are indicated as version 0, suggesting early or initial releases of OpenMQ are impacted. The vulnerability is assigned CWE identifiers related to use of default credentials and improper authentication enforcement.
Potential Impact
The impact of CVE-2026-22886 is severe for organizations worldwide using Eclipse OpenMQ, particularly those exposing the management service on networks accessible to attackers. Successful exploitation results in full administrative control over the messaging broker, enabling attackers to intercept, modify, or delete messages, disrupt messaging services, and potentially use the compromised broker as a foothold for lateral movement within the network. This can lead to data breaches, service outages, and loss of trust in critical messaging infrastructure. Industries relying on OpenMQ for asynchronous communication, such as financial services, telecommunications, healthcare, and government, face heightened risk due to the critical nature of message integrity and availability. The vulnerability’s ease of exploitation and lack of required authentication or user interaction increase the likelihood of attacks, especially in environments with weak network segmentation or exposed management interfaces. The absence of mandatory password changes on first use exacerbates the risk, as many deployments may unknowingly operate with default credentials. The overall impact includes potential large-scale disruption of enterprise messaging systems, data compromise, and operational downtime.
Mitigation Recommendations
To mitigate CVE-2026-22886, organizations should immediately audit their Eclipse OpenMQ deployments to identify if the imqbrokerd management service is enabled and accessible over the network. If the service is not required, it should be disabled entirely to eliminate the attack surface. For deployments requiring management access, the default administrative credentials must be changed immediately to a strong, unique password. Since the product does not enforce password changes, manual intervention is necessary. Network-level controls such as firewall rules or VPNs should restrict access to the management service port to trusted administrators only. Additionally, organizations should implement monitoring and alerting for unusual authentication attempts or administrative actions on the broker. Regular vulnerability scanning and configuration reviews should be conducted to ensure no default credentials remain in use. Finally, organizations should track vendor updates and apply patches or configuration changes once available to address this vulnerability at the software level.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-01-23T11:07:26.448Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69a6aadfd1a09e29cbf4c05c
Added to database: 3/3/2026, 9:33:19 AM
Last enriched: 3/3/2026, 9:47:37 AM
Last updated: 3/4/2026, 3:36:25 AM
Views: 18
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27012: CWE-306: Missing Authentication for Critical Function in devcode-it openstamanager
CriticalCVE-2026-28289: CWE-434: Unrestricted Upload of File with Dangerous Type in freescout-help-desk freescout
CriticalCVE-2026-27971: CWE-502: Deserialization of Untrusted Data in QwikDev qwik
CriticalCVE-2026-2292: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in bandido Morkva UA Shipping
MediumCVE-2026-2289: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in taskbuilder Taskbuilder – Project Management & Task Management Tool With Kanban Board
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.