Cyber Resilience

CVE-2025-2950

Ibm I 7.3 … 7.6

Published
18 April 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-2950 is a medium-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Ibm I. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

IBM i 7.3, 7.4, 7.5, and 7.5 is vulnerable to a host header injection attack caused by improper neutralization of HTTP header content by IBM Navigator for i. An authenticated user can manipulate the host header in HTTP requests to…

more

change domain/IP address which may lead to unexpected behavior.

CWE(s)
CWE-644

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-23470Same product: Ibm I
CVE-2024-40686Same vendor: Ibm
CVE-2026-10852Same product: Ibm I
CVE-2023-30988Same product: Ibm I
CVE-2024-51464Same product: Ibm I
CVE-2023-38721Same product: Ibm I
CVE-2024-51463Same product: Ibm I
CVE-2023-43064Same product: Ibm I
CVE-2023-40686Same product: Ibm I
CVE-2024-31890Same product: Ibm I

Affected Assets

ibm
i
7.3, 7.4, 7.5, 7.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V4.2.3

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly requires checking/neutralizing untrusted data such as HTTP headers before they reach browser components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing catches header-injection issues before release, covering most of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.

References