VulnerabilityPublished 26 Jun 2025Updated 8 Jan 2026

CVE-2025-5731: Red Hat infinispan · Generation of Error Message Containing Sensitive Information

Affects Red Hat infinispanSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.infinispan/infinispan`pkg:maven/org.infinispan/infinispan`Other threats	Affected =0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-5731, organizations should implement the following specific measures: 1) Restrict access to the Infinispan CLI to trusted administrators only, minimizing the risk of unauthorized local access. 2) Configure Kubernetes and Infinispan logging to exclude sensitive information from error messages and logs, ensuring that plaintext secrets are not recorded or displayed. 3) Employ environment hardening by enforcing strict role-based access controls (RBAC) and least privilege principles for users interacting with Infinispan and Kubernetes secrets. 4) Monitor CLI usage and error logs for unusual activity that might indicate attempts to trigger error messages containing sensitive data. 5) Stay updated with Red Hat advisories and apply patches or updates as soon as they become available to address this vulnerability. 6) Consider implementing secret management solutions that avoid embedding sensitive data directly in command strings or error outputs. 7) Conduct security reviews and testing focused on error handling and secret exposure in the deployment environment to identify and remediate similar issues proactively.

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.

Impact

The primary impact of CVE-2025-5731 is the potential exposure of sensitive passwords decoded from Kubernetes secrets through error messages in the Infinispan CLI. This leakage compromises confidentiality, potentially allowing unauthorized users with access to CLI error outputs or logs to obtain credentials that could be used to escalate privileges or access other systems. Although the vulnerability requires local access with low privileges, it could facilitate lateral movement within an environment if attackers gain initial footholds. The integrity and availability of systems are not directly affected. Organizations relying on Infinispan within Kubernetes clusters are at risk, especially if error messages are not properly secured or sanitized. The exposure of secrets can undermine trust in the security of containerized applications and may lead to compliance violations or data breaches. Since no known exploits are currently in the wild, the immediate risk is moderate, but the vulnerability should be addressed promptly to prevent future exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 15:31 UTC

Technical details

References

Community reviews

Related threats