# CVE-2025-5731: Infinispan: credential leakage in infinispan cli

> Attackers can view sensitive Kubernetes secret passwords in plaintext via error messages when executing invalid commands in the Infinispan CLI.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2025
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-cqm8-rg2p-jfcf

## What is CVE-2025-5731?

CVE-2025-5731 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 26 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in Infinispan CLI. A sensitive password, decoded from a Base64-encoded Kubernetes secret, is processed in plaintext and included in a command string that may expose the data in an error message when a command is not found.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

2 open source packages ship an affected version, including org.infinispan:infinispan-cli-client. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.infinispan:infinispan-cli-client` | Maven | All versions to 16.0.0.Dev01 | None |
| `org.infinispan:infinispan-cli-client` | Maven | All versions to 16.0.0.Dev01 | None |

Products: Infinispan Infinispan, Redhat Data Grid, Redhat Jboss Enterprise Application Platform, Redhat Jboss Enterprise Application Platform Expansion Pack.

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

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

## Is CVE-2025-5731 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2018-1131](https://insights.sbomify.com/CVE-2018-1131/): Deserialization of Untrusted Data in Infinispan (high 8.8)
- [CVE-2017-15089](https://insights.sbomify.com/CVE-2017-15089/): Deserialization of Untrusted Data in Infinispan (high 8.8)
- [CVE-2019-10174](https://insights.sbomify.com/CVE-2019-10174/): Use of Externally-Controlled Input to Select Classes or Code in Infinispan (high 7.5)
- [CVE-2023-5384](https://insights.sbomify.com/CVE-2023-5384/): Infinispan: credentials returned from configuration as clear text (high 7.2)
- [CVE-2023-3628](https://insights.sbomify.com/CVE-2023-3628/): Infispan: rest bulk ops don't check permissions (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5731 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 26 Jun 2025. 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-5731 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.infinispan:infinispan-cli-client (Maven): affected all versions up to 16.0.0.Dev01; no fix listed
- org.infinispan:infinispan-cli-client (Maven): affected all versions up to 16.0.0.Dev01; no fix listed

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-5731/ (Markdown: https://insights.sbomify.com/CVE-2025-5731/index.md)
```

## Sources

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

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