CVE-2016-0260
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 · uneditedMemory leak in queue-manager agents in IBM WebSphere MQ 8.x before 8.0.0.5 allows remote attackers to cause a denial of service (heap memory consumption) by triggering many errors.
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 confidenceA memory leak exists in queue-manager agents within IBM WebSphere MQ version 8.x prior to 8.0.0.5. The vulnerability allows remote attackers to trigger repeated error conditions, causing heap memory consumption to grow unbounded until the queue-manager exhausts available memory and becomes unresponsive.
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 data= 8.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Determine IBM WebSphere MQ installed versionRun the 'dspmqver' command or check the installation directory for version information. On Linux/Unix: /opt/mqm/bin/dspmqver. On Windows: check the installation via control panel or run 'mqconfig' if available.Affected if The version shown is 8.0, 8.0.0.1, 8.0.0.2, 8.0.0.3, or 8.0.0.4.
-
Identify active queue-managersUse the 'runmqsc -q' command or 'dspmq' command to list all queue-managers and their status. Check which queue-managers are in running state.Affected if Any queue-manager is running on an affected version of WebSphere MQ 8.x prior to 8.0.0.5.
-
Verify queue-manager agent configurationsInspect queue-manager configuration files and running processes related to the queue-manager. Use 'runmqsc QMGRNAME' to display queue manager attributes and agent channel configurations.Affected if Queue-manager agents are configured and active on a vulnerable version.
-
Monitor heap memory consumptionObserve the memory usage of queue-manager processes (typically runmqbm or amqzxma0 processes) over time. Use system monitoring tools like 'ps', 'top', or Windows Task Manager to track growing heap usage.Affected if Memory usage of queue-manager processes grows continuously without stabilizing, indicating the leak is active.
A system is affected if IBM WebSphere MQ version 8.0.x (where x is 0-4) is installed and queue-managers are running, as the memory leak in queue-manager agents will cause unbounded heap growth under repeated error conditions.
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 dataApply IBM WebSphere MQ patch 8.0.0.5 or later to resolve the memory leak in queue-manager agents.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0260 — 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-2016-0260 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