Menu

Star on GitHub · 3.2k

CVE-2025-2667

2.7 · LOW

IBM Sterling B2B Integrator 6.0.0.0 through 6.1.2.7_1 and 6.2.0.0 through 6.2.0.4 and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7_1 and 6.2.0.0 through 6.2.0.4 could disclose sensitive system…

Published Sep 4, 2025CWE-497EPSS 0.26%

Overview

CVE-2025-2667 is a low-severity vulnerability. It was published on September 4, 2025 and has a CVSS 3.1 base score of 2.7 (LOW).

This vulnerability has a CVSS 3.1 base score of 2.7, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

IBM Sterling B2B Integrator 6.0.0.0 through 6.1.2.7_1 and 6.2.0.0 through 6.2.0.4 and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7_1 and 6.2.0.0 through 6.2.0.4 could disclose sensitive system information about the server to a privileged user that could aid in further attacks against the system.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-2667?

CVE-2025-2667 is a low-severity vulnerability. It was published on September 4, 2025 and has a CVSS 3.1 base score of 2.7 (LOW).

How severe is CVE-2025-2667?

This vulnerability has a CVSS 3.1 base score of 2.7, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-2667?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-2667?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-2667 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2025

View all