dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2025-33003

HIGH · 7.8 CVSS v3.1 Published 2025-10-31
Fix available
A fix is available. Upgrade to after 11.7.1.6 or later.
See remediation →
80/100
Remediation priority · High
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 could allow a non-root user to gain higher privileges/capabilities within the scope of a container due to execution with unnecessary privileges.

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

IBM InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6 run inside containers with excessive privileges, allowing a non-root user within the container to escalate to root or obtain additional Linux capabilities by exploiting unnecessary elevated permissions.

MitigationReconfigure the container to run with minimal privileges: drop all unnecessary Linux capabilities, run as a non-root user, and ensure the container only has capabilities explicitly required for the application to function.

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, <= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if IBM InfoSphere Information Server is running in a container
    List running containers using 'docker ps' or 'podman ps' and look for container names or images containing 'infosphere' or 'iis'. Alternatively, check for processes related to IBM InfoSphere.
    Affected if A container running IBM InfoSphere Information Server is found
  2. Check the installed version of IBM InfoSphere Information Server
    Inspect the container or check the installed version within the container. Common locations include: check the product version file, label, or environment variable. Compare against the affected range: 11.7.0.0 through 11.7.1.6.
    Affected if The version falls within 11.7.0.0 to 11.7.1.6 inclusive
  3. Verify if the container runs as root user
    Run 'docker inspect <container_id>' or 'podman inspect <container_id>' and check the 'User' field in the SecurityConfig section. If empty or showing '0' or 'root', the container runs as root.
    Affected if The container runs as root user (UID 0) or the User field is empty
  4. Check for excessive Linux capabilities granted to the container
    Run 'docker inspect <container_id>' or 'podman inspect <container_id>' and examine the 'CapAdd' or 'Capabilities' array. Also check for '--privileged' flag using 'docker inspect' or 'podman inspect'.
    Affected if The container has CAP_SYS_ADMIN, CAP_NET_ADMIN, or all capabilities (--privileged mode is enabled), or has capabilities beyond what the application requires
  5. Inspect container security context configuration
    Check the container's security context settings in the deployment configuration or orchestration manifest (Kubernetes YAML, Docker Compose, etc.) for 'runAsNonRoot: false', 'privileged: true', or missing security settings.
    Affected if The security context is not configured to drop all capabilities or run as non-root

The environment is affected if IBM InfoSphere Information Server version 11.7.0.0 through 11.7.1.6 is running in a container configured to run as root or with elevated Linux capabilities beyond what is strictly necessary.

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

Reconfigure the container to run with minimal privileges: drop all unnecessary Linux capabilities, run as a non-root user, and ensure the container only has capabilities explicitly required for the application to function.

Fix this in Infosphere Information Server 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 the upgrade done

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-33003 — 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-33003 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