| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Eclipse OpenMQ. It has been rated as very critical. This affects an unknown part. Performing a manipulation results in default credentials. This vulnerability is reported as CVE-2026-22886. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as very critical, was found in Eclipse OpenMQ (version unknown). This affects an unknown function. The manipulation with an unknown input leads to a default credentials vulnerability. CWE is classifying the issue as CWE-1392. The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was disclosed by Camilo G.. The advisory is shared at gitlab.eclipse.org. This vulnerability is uniquely identified as CVE-2026-22886 since 01/23/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/04/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (eclipse): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Default credentialsCWE: CWE-1392
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/23/2026 CVE reserved03/03/2026 Advisory disclosed
03/03/2026 VulDB entry created
03/04/2026 VulDB entry last update
Sources
Advisory: gitlab.eclipse.orgResearcher: Camilo G.
Status: Confirmed
CVE: CVE-2026-22886 (🔒)
GCVE (CVE): GCVE-0-2026-22886
GCVE (VulDB): GCVE-100-348537
Entry
Created: 03/03/2026 11:00Updated: 03/04/2026 19:48
Changes: 03/03/2026 11:00 (60), 03/04/2026 19:48 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.