dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2025-36124

HIGH · 7.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 25.0.0.9 or later.
See remediation →
84/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 Liberty 17.0.0.3 through 25.0.0.8 could allow a remote attacker to bypass security restrictions caused by a failure to honor JMS messaging configuration

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 25.0.0.8 fails to properly honor JMS (Java Message Service) messaging security configuration, allowing a remote attacker to potentially bypass security restrictions. The vulnerability stems from incorrect handling of JMS security settings in the Liberty profile.

MitigationApply the IBM fix for this vulnerability (check IBM security bulletins for CVE-2025-36124) or upgrade to a patched version of WebSphere Liberty beyond 25.0.0.8. Review JMS messaging security configurations to ensure they are being properly 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:>= 17.0.0.3, < 25.0.0.9

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 WebSphere Liberty installation and version
    Locate the Liberty installation directory and check the version. In the Liberty root directory, examine the file 'product-info/product-version' or run 'java -jar wlp-webProfileX.jar --version' if available. Alternatively, check the 'lib/versions' directory for version information.
    Affected if The installed version falls within 17.0.0.3 through 25.0.0.8 inclusive.
  2. Verify JMS messaging features are enabled
    Examine the server.xml configuration file (typically in the wlp/usr/servers/<serverName>/ directory). Look for JMS-related feature definitions such as 'messaging-3.0', 'messaging-2.0', 'jms-2.0', or older 'jms-1.0' features in the <featureManager> section.
    Affected if JMS messaging features are enabled in the server configuration.
  3. Inspect JMS security configuration settings
    Review the server.xml file for JMS security-related configuration elements. Look for <jmsQueue> or <jmsTopic> definitions with security settings, and check for <security> or <jaasLogin> entries that control JMS message security. Also inspect any resource adapter configurations related to JMS.
    Affected if JMS messaging security is configured but the configuration may not be properly enforced due to the vulnerability.
  4. Check for JMS message-driven bean deployments
    Examine the applications deployed in the Liberty profile. Look for message-driven beans (MDBs) or JMS client applications in the 'usr/servers/<serverName>/apps' directory or deployed EAR/WAR files. Check corresponding XML deployment descriptors for JMS destination configurations.
    Affected if Applications using JMS message-driven beans or JMS producers/consumers are deployed.

You are affected if your WebSphere Liberty version is between 17.0.0.3 and 25.0.0.8 inclusive AND you have JMS messaging features enabled with security configurations that may not be properly honored.

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 25.0.0.9 or later
Fixed in 25.0.0.9
Interim mitigation

Apply the IBM fix for this vulnerability (check IBM security bulletins for CVE-2025-36124) or upgrade to a patched version of WebSphere Liberty beyond 25.0.0.8. Review JMS messaging security configurations to ensure they are being properly enforced.

Recommended fix High confidence

25.0.0.9 or later (preferably latest 25.0.x release)

  1. 1. Back up the current WebSphere Application Server Liberty installation and configuration
  2. 2. Download IBM WebSphere Application Server Liberty version 25.0.0.9 or later from IBM's official Fix Central or entitlement repository
  3. 3. Install the new version following IBM's installation documentation for your deployment model
  4. 4. Validate JMS messaging configuration is properly honored in the new version
  5. 5. Test the upgrade in a non-production environment before deploying to production
  6. 6. Deploy the validated upgrade to production environments

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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