dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-11546

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 26.0.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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.7 is affected by a server-side request forgery vulnerability with the adminCenter-1.0 feature enabled.

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 WebSphere Application Server Liberty versions 17.0.0.3 through 26.0.0.7 contains a server-side request forgery (SSRF) vulnerability in the adminCenter-1.0 feature. When this feature is enabled, an unauthenticated remote attacker can coerce the server into making arbitrary HTTP requests to internal or external resources, potentially bypassing network segmentation and accessing sensitive internal services.

MitigationDisable the adminCenter-1.0 feature if not required, or upgrade to a patched version beyond 26.0.0.7. Implement network segmentation and firewall rules to restrict outbound connections from the application server.

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.8

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm IBM WebSphere Application Server Liberty is installed
    Locate the installation directory and verify the product is IBM WebSphere Application Server Liberty. Check for the Liberty installation path (typically $WLP_HOME or similar) and identify if this is the Liberty profile, not traditional WebSphere.
    Affected if The product is IBM WebSphere Application Server Liberty
  2. Determine the installed Liberty version
    Check the version by examining the lib/versionInfo.xml file in the Liberty installation directory, or run the productInfo version command if available. Compare the version number against the affected range 17.0.0.3 through 26.0.0.7.
    Affected if The installed version is 17.0.0.3 or higher but lower than 26.0.0.8
  3. Inspect server.xml for adminCenter-1.0 feature
    Open the server.xml configuration file (located in the servers/<serverName> directory under the Liberty user directory or in the wlp/usr/servers/<serverName> path). Search for a featureManager section containing <feature>adminCenter-1.0</feature>.
    Affected if The adminCenter-1.0 feature is listed as enabled in the server.xml featureManager section
  4. Verify adminCenter is publicly accessible
    Confirm the adminCenter-1.0 feature is exposed on a network-accessible port. Check the httpEndpoint configuration in server.xml to see if the adminCenter is bound to an external interface (0.0.0.0) rather than localhost only.
    Affected if The adminCenter-1.0 feature is enabled AND accessible from network interfaces other than localhost

A user is affected if they are running IBM WebSphere Application Server Liberty version 17.0.0.3 through 26.0.0.7 with the adminCenter-1.0 feature enabled and exposed on a network-accessible endpoint.

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.8 or later
Fixed in 26.0.0.8
Interim mitigation

Disable the adminCenter-1.0 feature if not required, or upgrade to a patched version beyond 26.0.0.7. Implement network segmentation and firewall rules to restrict outbound connections from the application server.

Recommended fix High confidence

IBM WebSphere Application Server Liberty 26.0.0.8 or later

  1. Back up your current WebSphere Application Server configuration and deployment assets
  2. Review the IBM WebSphere Application Server Liberty 26.0.0.8 release notes for migration considerations and known issues
  3. Download IBM WebSphere Application Server Liberty version 26.0.0.8 or later from IBM Fix Central or your authorized IBM distribution channel
  4. Test the upgrade in a non-production environment before deploying to production
  5. Deploy the upgrade to production environment
  6. Verify the adminCenter-1.0 feature functions correctly after upgrade
Caveat Review IBM release notes for any compatibility changes between your current version and 26.0.0.8; minor version upgrades typically have low risk but test thoroughly

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

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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