CVE-2026-22886
Eclipse Openmq
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-22886 is a critical-severity Use of Weak Credentials (CWE-1391) vulnerability in Eclipse Openmq. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and IA-5 (Authenticator Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22886 is a critical vulnerability in OpenMQ, specifically affecting its TCP-based management service known as imqbrokerd. The issue arises because OpenMQ ships with a default administrative account using the credentials admin/admin, and the service requires authentication by default but does not enforce a mandatory password change on first use. After the initial successful login, the server continues to accept the default password indefinitely, without any warnings or enforcement mechanisms.
A remote attacker with network access to the exposed service port can exploit this vulnerability by authenticating with the unchanged default credentials, thereby gaining full control over the broker's administrative features. In real-world deployments, the management service is often left enabled without modifying the default credentials, making exploitation straightforward. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWEs 1391, 1392, and 1393.
Mitigation details are available in the advisory referenced at https://gitlab.eclipse.org/security/cve-assignment/-/issues/85, published on 2026-03-03.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9283
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 3 OS baselines
V6.2.2V13.2.1V6.3.1V6.3.2
Mitigating Controls (NIST 800-53 r5) AI
IA-5 directly requires management of authenticator strength, distribution, and replacement, stopping default or guessable credentials from being introduced or used.
Secure configuration settings establish baselines that prohibit default credentials on system components.
Vulnerability scanning can discover default credentials after deployment but does not stop their introduction.
Account management processes include assignment and control of initial account credentials, reducing the chance defaults remain active.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Credential management directly requires replacing default passwords with unique, strong credentials.
Hardened baselines and configuration management explicitly prohibit default credentials on deployed systems.
Password-strength policies in PR.AA-03 directly block weak authenticators, but the control leaves hard-coded/default credentials largely unaddressed.
Vulnerability scanning will discover default-password instances, enabling remediation, yet does not itself prevent their initial use.
Authorization policies assume credentials already exist and are not default; least-privilege helps limit impact but does not prevent defaults.
Training raises password-hygiene awareness and can therefore reduce some weak-credential mistakes, yet supplies no enforcement mechanism and leaves the dominant technical sources of CWE-1391 untouched.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Directly requires secure generation, distribution and storage of authentication credentials, eliminating default/hard-coded weak passwords.
Mandates secure authentication mechanisms that preclude use of weak or default credentials.
Secure-coding rules can prohibit hard-coded passwords, yet coverage depends on specific coding standards adopted.
Security testing can discover weak credentials, but does not guarantee they are prevented by design.
Enforces secure baseline configurations that should remove default credentials, yet does not guarantee credential strength.
Restricts privileged accounts but does not explicitly address default or hard-coded credentials for those accounts.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248667 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391
- V-248668 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. prevents CWE-1391
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-1391
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1391
RHEL 8 (1 rule)
- V-244533 RHEL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391