dbcve.org
IApplication · Ibm

CVE-2025-2950

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 change domain/IP address which may lead to unexpected behavior.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Host header injection vulnerability in IBM Navigator for i on IBM i versions 7.3, 7.4, and 7.5. An authenticated attacker can manipulate the HTTP Host header to change the domain/IP address, potentially leading to cache poisoning, password reset manipulation, or redirecting responses to attacker-controlled servers.

MitigationApply IBM security patches when released. In the interim, implement WAF rules or web server configuration to validate and normalize Host headers against an allowlist of expected values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IApplication
Affected:= 7.3= 7.4= 7.5= 7.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify IBM i operating system version
    Run command: DSPSFWRSC (Display Software Resources) or WRKOBJ of system value QSMWRSVR to identify the IBM i release. Alternatively, use 'system -i' command or check the welcome screen for version number.
    Affected if The version is 7.3, 7.4, 7.5, or 7.6 and IBM Navigator for i is installed and accessible.
  2. Confirm IBM Navigator for i is installed
    Check if the Navigator for i HTTP server instance is configured. Use WRKACTJOB JOB(QHTTPSVR) or look for QIBM_HTTP_SERVER_* jobs. Verify the product is licensed and installed using GO LICPGM option 10.
    Affected if Navigator for i is installed and the HTTP server is running.
  3. Identify if Navigator for i web interface is exposed
    Check HTTP server configuration files in /www directory (e.g., /www/navigator or /www/IBMi Navigator). Verify port accessibility via NETSTAT *CNN or check if the service listens on ports 2001, 2010, or configured ports.
    Affected if The Navigator for i web interface is accessible over the network to authenticated users.
  4. Inspect web server Host header handling
    Review the HTTP server configuration (httpd.conf) for any Host header validation rules. Check for directives like 'UseCanonicalName' or 'Require host' entries that validate the Host header against an allowlist.
    Affected if No Host header validation is configured in the web server (the default configuration allows arbitrary Host headers).

You are affected if running IBM i 7.3 through 7.6 with IBM Navigator for i installed and its web interface is accessible, and the HTTP server lacks Host header validation rules.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM security patches when released. In the interim, implement WAF rules or web server configuration to validate and normalize Host headers against an allowlist of expected values.

Recommended fix Moderate confidence

IBM i 7.3, 7.4, 7.5, or 7.6 to the fixed PTF/release level as specified in IBM security bulletin

  1. Check IBM's official security bulletin for CVE-2025-2950 at ibm.com to obtain the specific PTF (Program Temporary Fix) or fixed release level
  2. Apply the recommended IBM i PTF or upgrade to the fixed release level for your IBM i version (7.3, 7.4, 7.5, or 7.6)
  3. Verify the fix by reviewing IBM Navigator for i behavior after applying the update
Caveat Verify application compatibility with the IBM i PTF or release before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in I Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2950 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data