# CVE-2025-12755: Multiple vulnerabilities in IBM MQ Operator and Queue manager container images

> An attacker can inject malicious data into IBM MQ log files, causing log manipulation and misleading audit trails.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-846m-xcgv-cmm3

## What is CVE-2025-12755?

CVE-2025-12755 is a medium-severity vulnerability in IBM MQ Operator, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM MQ Operator (SC2 v3.2.0–3.8.1, LTS v2.0.0–2.0.29) and IBM‑supplied MQ Advanced container images (across affected SC2, CD, and LTS 9.3.x–9.4.x releases) contain a vulnerability where log messages are not properly neutralized before being written to log files. This flaw could allow an unauthorized user to inject malicious data into MQ log entries, potentially leading to misleading logs, log manipulation, or downstream log‑processing issues.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2025-12755?


## How do I fix CVE-2025-12755?

No fix has been published for CVE-2025-12755 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12755 being exploited?

There is no known exploitation of CVE-2025-12755 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12755 and fix it if it is affected.

What it is: CVE-2025-12755 is a medium-severity vulnerability in IBM MQ Operator, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12755 in the wild and no public exploit code.

Affected product: IBM MQ Operator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12755/ (Markdown: https://insights.sbomify.com/CVE-2025-12755/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12755
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12755
- OSV: https://osv.dev/vulnerability/CVE-2025-12755

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12755/
Summaries are generated and may contain mistakes; the official description above is the record.