CVE-2026-12669: IBM MQ Out-of-bounds Read
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: IBM MQ Operator 3.4.0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to IBM MQ Operator 3.4.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
IBM MQ could allow an authenticated attacker to trigger a minor out-of-bounds read when sending malformed compressed data, though the data is not disclosed and the request is rejected.
- Published
- Oct 19, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-125
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.3
- CNA · ibm
- 3.1
- 1.2 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ibm | mq operator | cpe:2.3:a:ibm:mq_operator |
| ibm | supplied mq advanced container images | cpe:2.3:a:ibm:supplied_mq_advanced_container_images |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm mq operator2.0.0 and later · up to 2.0.29 inclusive
- ibm mq operator3.2.0 and later · up to 3.2.29 inclusive
- ibm mq operator3.3.0
- ibm mq operator3.4.0
- ibm mq operator3.4.1
- ibm mq operator3.5.0
- ibm mq operator3.5.1
- ibm mq operator3.5.2
- ibm mq operator3.5.3
- ibm mq operator3.6.0
- ibm mq operator3.6.1
- ibm mq operator3.6.2
- ibm mq operator3.6.3
- ibm mq operator3.6.4
- ibm mq operator3.7.0
- ibm mq operator3.7.1
- ibm mq operator3.7.2
- ibm mq operator3.8.0
- ibm mq operator3.8.1
- ibm mq operator3.9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM MQ Advanced container images
- 9.4.0.6-r2, 9.4.0.7-r1, 9.4.0.10-r1, 9.4.0.10-r2, 9.4.0.11-r1, 9.4.0.11-r2, 9.4.0.11-r3, 9.4.0.12-r1, 9.4.0.16-r1, 9.4.0.16-r2, 9.4.0.17-r1, 9.4.0.17-r2 … (+23)affected
- 9.4.0.6-r1 and later · up to and including r1, 9.4.0.6-r2, 9.4.0.7-r1, 9.4.0.10-r1, 9.4.0.10-r2, 9.4.0.11-r1, 9.4.0.11-r2, 9.4.0.11-r3, 9.4.0.12-r1, 9.4.0.15-r1 - 9.4.0.15-r4, 9.4.0.16-r1, 9.4.0.16-r2, 9.4.0.17-r1, 9.4.0.17-r2, 9.4.0.20-r1, 9.affected · semver
- 9.4.0.15-r1 and later · up to and including 9.4.0.15-r4affected
- 9.4.0.25-r1 and later · up to and including 9.4.0.25-r3affected
- 9.4.3.1-r1 and later · up to and including 9.4.3.1-r3affected
- 10.0.0.0-r1 and later · up to and including 10.0.0.0-r4affected
IBM MQ Operator
- 3.4.1, 3.5.0, 3.8.0, 3.8.1, 3.9.0, 3.9.1, 3.9.2, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4affected
- 3.2.0 and later · up to and including 3.2.29affected · semver
- 3.3.0 and later · before 3.4.0affected · semver
- 3.5.1 and later · up to and including 3.5.3affected · semver
- 3.6.0 and later · up to and including 3.6.4affected · semver
- 3.7.0 and later · up to and including 3.7.2affected · semver
- 2.0.0 and later · up to and including 2.0.29affected · semver
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-12665IBM MQ Buffer Overflow39Monitor
- CVE-2025-36041IBM MQ improper certificate validation39Monitor
- CVE-2024-39742IBM MQ Container authentication bypass39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-12350Oct 19, 2026 · IBM MQ Deserialization of Untrusted Data26Monitor
- ← EarlierCVE-2026-12660Oct 19, 2026 · IBM MQ Path Traversal10Monitor
- Later →CVE-2026-12670Oct 19, 2026 · IBM MQ Denial of Service26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| IBM MQ Operator | 3.4.0 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 3, 2026+14 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1357 · Oct 20, 2026(IBM Çoklu Ürün Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- CVSS3.1 → 4.3
- Severitylow → medium
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.