CVE-2026-11714
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 · uneditedIBM WebSphere Application Server Liberty is affected by a server-side request forgery vulnerability with the apiDiscovery-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 confidenceIBM WebSphere Application Server Liberty versions 17.0.0.3 through 26.0.0.7 contain a server-side request forgery (SSRF) vulnerability in the apiDiscovery-1.0 feature. An attacker can exploit this to make the server perform unintended requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or pivoting into protected networks.
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>= 17.0.0.3, < 26.0.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check WebSphere Liberty versionRun the productInfo version command from the Liberty installation bin directory, or read the version manifest from the wlp/lib/versions/websphereliberty.jar fileAffected if The installed version is 17.0.0.3 through 26.0.0.7 inclusive (versions below 17.0.0.3 or at 26.0.0.8 and later are not affected)
-
Identify the server configuration directoryLocate the server.xml file in the wlp/usr/servers/<serverName>/ directory for your configured Liberty server instanceAffected if A server.xml configuration file exists for the server
-
Verify if apiDiscovery-1.0 feature is enabledOpen the server.xml file and search within the <featureManager> section for a <feature> element containing apiDiscovery-1.0Affected if The apiDiscovery-1.0 feature is present in the featureManager section, indicating the vulnerable feature is enabled
A server is affected only if both conditions are true: the installed Liberty version falls within 17.0.0.3 to 26.0.0.7 AND the apiDiscovery-1.0 feature is explicitly enabled in the server.xml configuration
Generated from the published advisory. Verify against your own configuration.
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 · scoped26.0.0.8
Disable the apiDiscovery-1.0 feature in the server configuration if not required, or apply vendor patches when available. If the feature is business-critical, implement strict network segmentation and restrict outbound connectivity to trusted destinations only.
WebSphere Application Server Liberty 26.0.0.8
- Download IBM WebSphere Application Server Liberty version 26.0.0.8 or later from IBM Fix Central or Passport Advantage
- Backup your current configuration and applications
- Install the new version following IBM's standard installation procedure
- Deploy your saved configuration and applications to the new version
- Verify the apiDiscovery-1.0 feature functions correctly in the updated environment
- Test that the SSRF vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11714 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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