dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-10845

HIGH · 7.3 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 8.5.5.30 / 9.0.5.29 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 8.5 and 9.0 could allow a remote attacker to bypass authentication and gain unauthorized access to JAX-WS applications.

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 8.5 and 9.0 contains an authentication bypass vulnerability in JAX-WS (Java API for XML Web Services) that allows remote attackers to circumvent authentication mechanisms and gain unauthorized access to web services endpoints.

MitigationApply IBM security patches for this vulnerability and review JAX-WS endpoint authentication configuration to ensure proper access controls are enforced.

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:>= 8.5.0.0, < 8.5.5.30>= 9.0.0.0, < 9.0.5.29

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
Low
Integrity
Low
Availability
Low

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

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. Determine installed WebSphere Application Server version
    Run the versionInfo command from the WebSphere bin directory: versionInfo -long or check the install directory for version files. Alternatively, log into the WebSphere Admin Console and check the runtime version information.
    Affected if The installed version is >= 8.5.0.0 and < 8.5.5.30, OR >= 9.0.0.0 and < 9.0.5.29
  2. Identify if JAX-WS web services are deployed
    Check the WebSphere application deployment descriptors for JAX-WS endpoints. Look in the installedApps directory for WAR or EAR files containing web service definitions (wsdl files, JAX-WS annotations, or sun-jaxws.xml descriptors). In the Admin Console, navigate to Applications > Application Types > WebSphere enterprise applications and inspect for web service bindings.
    Affected if JAX-WS web services endpoints are deployed and exposed
  3. Verify web services endpoint authentication configuration
    In WebSphere Admin Console, go to Applications > Application Types > WebSphere enterprise applications > [select app] > Web Services: Default policies for SOAP and check the authentication settings. Also inspect the web.xml deployment descriptor for security constraints on web service URLs (look for <security-constraint> elements covering the service endpoint paths).
    Affected if No explicit authentication constraints are configured on the JAX-WS endpoint URLs, or authentication is set to NONE/OPTIONAL when it should be REQUIRED
  4. Check for unauthenticated JAX-WS endpoint access
    Review the ibm-webservices-ext.xml and ibm-webservices-bnd.xmi files in the deployed application META-INF or WEB-INF directories. Look for <security:WebServicesSecurity> configurations. Verify whether the authentication-mode attribute is missing or set to an insecure value.
    Affected if The WebServicesSecurity configuration allows unauthenticated access or has authentication-mode set to none or not configured

You are affected if your WebSphere version falls within 8.5.0.0-8.5.5.29 or 9.0.0.0-9.0.5.28 AND you have JAX-WS web services endpoints deployed WITHOUT proper authentication constraints configured.

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 8.5.5.30 / 9.0.5.29 or later
Fixed in 8.5.5.309.0.5.29
Interim mitigation

Apply IBM security patches for this vulnerability and review JAX-WS endpoint authentication configuration to ensure proper access controls are enforced.

Recommended fix High confidence

WebSphere Application Server 8.5.5.30 or later for 8.5.x; WebSphere Application Server 9.0.5.29 or later for 9.0.x

  1. 1. Identify the current version of IBM WebSphere Application Server using the versionInfo command or admin console
  2. 2. For WebSphere 8.5.x versions (8.5.0.0 through 8.5.5.29): Plan upgrade to version 8.5.5.30 or later
  3. 3. For WebSphere 9.0.x versions (9.0.0.0 through 9.0.5.28): Plan upgrade to version 9.0.5.29 or later
  4. 4. Review IBM WebSphere Application Server migration and upgrade documentation before proceeding
  5. 5. Create a full backup of the current WebSphere configuration and all deployed applications
  6. 6. Download the appropriate fix pack from IBM Fix Central (search for WebSphere Application Server fix pack 8.5.5.30 or 9.0.5.29)
  7. 7. Apply the upgrade following IBM's standard installation procedures for your deployment type (Base or Network Deployment)
  8. 8. After upgrade, verify JAX-WS applications now properly enforce authentication
Caveat Review IBM migration guides for compatibility changes between your current version and the target fix pack; test all applications in a staging environment before production deployment

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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