IBM Sterling B2B Integrator and and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 could allow an unauthenticated attacker to send a specially crafted request that causes the application to crash.
CVE-2025-14031
HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 17, 2026
Last Modified
June 17, 2026
References (1)
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:14 UTCEG score recompute
- 2026-07-27 14:14 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-77
- CVE-2015-7541EG 10.0CRITICAL
- CVE-2015-1815EG 10.0EPSS p97HIGH
- CVE-2014-1905EG 10.0EPSS p95HIGH
- CVE-2013-2810EG 10.0EPSS p93HIGH
- CVE-2014-5470EG 9.8EPSS p95CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS p94CRITICAL
- CVE-2014-4982EG 9.8EPSS p91CRITICAL
Frequently asked(4)
What is CVE-2025-14031?
CVE-2025-14031 is a high vulnerability published on March 17, 2026. IBM Sterling B2B Integrator and and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.72, 6.2.0.0 through 6.2.0.51, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 could allow an unauthenticated attacker to send a specially crafted request that causes the application to crash.
When was CVE-2025-14031 disclosed?
CVE-2025-14031 was first published in the National Vulnerability Database on March 17, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2025-14031?
CVE-2025-14031 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-14031?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14031, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-14031
Is Your Infrastructure Affected by CVE-2025-14031?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.