dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2026-1015

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to after 11.7.1.6 or later.
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 InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

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 · high confidence

IBM InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6 contains a server-side request forgery (SSRF) vulnerability that allows authenticated attackers to send unauthorized HTTP requests from the server. This can enable network enumeration and internal service probing, potentially exposing internal systems or facilitating further attacks.

MitigationApply the vendor-supplied patch or upgrade to a version beyond 11.7.1.6. If patching is immediately impractical, implement network segmentation and restrict outbound connectivity from the affected server to limit the SSRF attack surface.

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
Infosphere Information ServerApplication
Affected:>= 11.7.0.0, <= 11.7.1.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. Identify installed IBM InfoSphere Information Server version
    Locate the version information in the IBM InfoSphere installation directory, typically in a version.txt file, or use the 'om.Version' command-line tool if available. Alternatively, check the IBM Installation Manager or the About dialog in the InfoSphere administration console.
    Affected if The installed version is 11.7.0.0, 11.7.0.1, 11.7.1.0, 11.7.1.1, 11.7.1.2, 11.7.1.3, 11.7.1.4, 11.7.1.5, or 11.7.1.6.
  2. Verify the DataStage client or web services are accessible
    Check if the IBM InfoSphere Information Server web interface (typically on ports 9443 or 9080) or DataStage client services are exposed and reachable from the network. Review web server configuration files such as server.xml or httpd.conf in the installation directory.
    Affected if The web administration console or DataStage web services are exposed externally or accessible without additional network segmentation.
  3. Review authentication configuration for web endpoints
    Examine the IBM InfoSphere user authentication settings in the IBM WebSphere Application Server console or the infoSphere configuration files. Verify that strong authentication is required for HTTP request-handling endpoints.
    Affected if Web endpoints that handle HTTP requests do not require strong authentication, or anonymous or weak authentication is permitted.
  4. Inspect outbound HTTP proxy settings
    Check the IBM InfoSphere configuration for HTTP proxy settings, typically found in the IBM WebSphere Application Server administrative console under 'Global HTTP proxy settings' or in the wrapper.conf file. Determine if the server is configured to allow arbitrary outbound HTTP connections.
    Affected if The server is configured to permit unrestricted outbound HTTP connections from the InfoSphere services.

You are affected if the installed IBM InfoSphere Information Server version falls within 11.7.0.0 through 11.7.1.6 AND the web-based services or HTTP-handling endpoints are accessible to authenticated users.

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.

From vendor data
Upgrade available Upgrade to a release after 11.7.1.6
Interim mitigation

Apply the vendor-supplied patch or upgrade to a version beyond 11.7.1.6. If patching is immediately impractical, implement network segmentation and restrict outbound connectivity from the affected server to limit the SSRF attack surface.

Fix this in Infosphere Information Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1015 — 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-2026-1015 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