What is the CVSS score of CVE-2025-0985?

CVE-2025-0985 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Which versions of Mq are affected by CVE-2025-0985?

CVE-2025-0985 presents moderate security risk rated CVSS 5.5. Exploitation could compromise the security of affected deployments.

How to fix or mitigate CVE-2025-0985?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Mq CVE-2025-0985

MEDIUM

Cleartext Storage of Sensitive Information in an Environment Variable (CWE-526)

2025-02-28 psirt@us.ibm.com

Information Disclosure IBM Mq

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:29 vuln.today

CVE Published

Feb 28, 2025 - 17:15 nvd

MEDIUM 5.5

DescriptionCVE.org

IBM MQ 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD

stores potentially sensitive information in environment variables that could be obtained by a local user.

AnalysisAI

IBM MQ 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD stores potentially sensitive information in environment variables that could be obtained by a local user. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-526. IBM MQ 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD stores potentially sensitive information in environment variables that could be obtained by a local user. Affected products include: Ibm Mq.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.