CVE-2026-22886
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenMQ 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenMQ's imqbrokerd TCP management service ships with hardcoded default credentials (admin/admin) and lacks any mechanism to enforce mandatory password changes on first use. After initial deployment, the default password remains valid indefinitely, allowing remote attackers with network access to authenticate as administrators and gain full control of the service's administrative features.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify OpenMQ installationLocate the OpenMQ installation directory and identify the imqbrokerd executable. On Linux/Unix, common paths include /opt/openmq or /opt/mq. Check for the presence of the imqbrokerd binary and associated configuration files in the installation directory.Affected if OpenMQ with imqbrokerd is installed and the management service is present on the system.
-
Identify management service port configurationExamine the OpenMQ instance configuration (typically in the /etc directory or under the installation root) for the imqbrokerd port settings. Look for properties files containing 'imq.port' or 'broker.port' entries, and check if the TCP management service is configured to listen on a network interface accessible remotely.Affected if The management service TCP port is configured and bound to a network interface accessible to potential attackers (not localhost-only or firewalled).
-
Locate password configuration fileFind the password or user authentication configuration file within the OpenMQ configuration directory. This is typically named 'passfile' or 'user.properties' and contains admin credential definitions. Check the immediate directory where imqbrokerd stores its configuration.Affected if A password configuration file exists and contains admin credentials without evidence of modification from defaults.
-
Check for default credential usageInspect the password configuration file to determine if the default username 'admin' is present with the default password 'admin'. Compare the stored password hash against known default values or attempt authorized authentication testing in a controlled, owned environment if permitted by policy.Affected if The admin account uses the default username 'admin' with default password 'admin' or the password has never been changed from initial deployment.
-
Verify password policy enforcementReview the imqbrokerd configuration for any settings that enforce mandatory password changes on first use or periodic password rotation. Check for properties like 'imq.password.required' or similar enforcement mechanisms in the broker configuration files.Affected if No password policy enforcement mechanism is configured and the default credentials remain valid indefinitely.
Your environment is affected if OpenMQ's imqbrokerd management service is exposed on the network and the default admin/admin credentials have not been changed from their default values.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately change the default administrative password to a strong, unique credential and implement password policy enforcement; if the management service is not required, disable it or restrict access to trusted IP addresses.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data