dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-1561

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 26.0.0.4 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 WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.3 IBM WebSphere Application Server Liberty is vulnerable to server-side request forgery (SSRF). This may allow remote 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 · moderate confidence

IBM WebSphere Application Server Liberty versions 17.0.0.3 through 26.0.0.3 contains a server-side request forgery (SSRF) vulnerability. An attacker can leverage this flaw to cause the server to make unauthorized requests to internal or external resources, enabling network enumeration, access to internal services/metadata, or serving as a pivot for further attacks.

MitigationApply the IBM fix (subsequent version beyond 26.0.0.3) when available. In the interim, implement network segmentation to restrict outbound connections from the application server, validate and sanitize any user-controlled URL inputs, and disable unnecessary network-facing features.

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
Websphere Application ServerApplication
Affected:>= 17.0.0.3, < 26.0.0.4

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 the installed WebSphere Liberty version
    Run the versionInfo command from the Liberty installation bin directory, or check the server startup logs for the Liberty version string. On Windows, you can also right-click the install directory and check properties.
    Affected if The installed version is 17.0.0.3 or higher but lower than 26.0.0.4
  2. Confirm network connectivity is enabled
    Verify that the server.xml configuration file (located in the wlp/usr/servers/<serverName> directory) contains network listeners or httpEndpoint elements. Check for enabled http or https ports that accept external connections.
    Affected if The server has active network listeners configured and is reachable over the network
  3. Check for exposed administrative or REST interfaces
    Review server.xml for features like adminCenter-1.0, restConnector-1.0, or any custom REST endpoints. These often handle URL parameters that could trigger SSRF.
    Affected if Administrative REST APIs or user-accessible endpoints that handle URLs are enabled and accessible
  4. Identify URL-handling features in server configuration
    Search server.xml and any included configuration files for elements that accept URL parameters, such as HTTP client configurations, proxy settings, or third-party feature configurations that fetch external resources.
    Affected if Features or custom code that processes user-supplied URLs are configured on the server

The server is affected if it runs IBM WebSphere Liberty version 17.0.0.3 through 26.0.0.3 and has network-accessible features that handle URL requests from 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.

dbcve · scoped
Upgrade available Upgrade to 26.0.0.4 or later
Fixed in 26.0.0.4
Interim mitigation

Apply the IBM fix (subsequent version beyond 26.0.0.3) when available. In the interim, implement network segmentation to restrict outbound connections from the application server, validate and sanitize any user-controlled URL inputs, and disable unnecessary network-facing features.

Recommended fix High confidence

26.0.0.4

  1. Download IBM WebSphere Application Server Liberty version 26.0.0.4 or later from IBM Fix Central or your authorized IBM distribution channel
  2. Review the IBM WebSphere Application Server Liberty upgrade documentation for your deployment type
  3. Back up your current WebSphere Liberty configuration, applications, and data
  4. Install version 26.0.0.4 in a test environment and verify application functionality
  5. After successful testing, schedule a maintenance window for production deployment
  6. Deploy the upgrade to production following your organization's change management procedures
  7. Verify the upgrade was successful and applications are functioning correctly

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

Fix this in Websphere Application 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-2026-1561 — 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-1561 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