CVE-2026-14525: IBM WebSphere Application Server Liberty is affected by an authenication bypass
IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.8 IBM WebSphere Application Server Liberty is vulnerable to an authentication bypass when the rtcomm-1.0 or rtcommGateway-1.0 feature is enabled.
Security readout for executives and security teams
Plain-English summary
A critical flaw can let an unauthenticated network attacker bypass authentication in affected IBM WebSphere Liberty deployments. Risk exists only when rtcomm-1.0 or rtcommGateway-1.0 is enabled. Successful exploitation could expose sensitive information, permit unauthorized changes, and cause limited service disruption.
Executive priority
Treat confirmed exposed configurations as an immediate remediation priority because compromise requires neither credentials nor user interaction. Rapidly establish whether affected features are enabled, reduce network exposure, and apply IBM's prescribed fix. Systems outside the feature-enabled condition are lower priority for this specific CVE.
Technical view
CVE-2026-14525 is a CWE-306 authentication bypass affecting IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.8 when either affected real-time communications feature is enabled. CVSS 3.1 is 9.4: network-reachable, low complexity, no privileges or user interaction, with high confidentiality and integrity impact and low availability impact.
Likely exposure
Exposure is limited to Liberty installations within the stated version range that enable rtcomm-1.0 or rtcommGateway-1.0. Internet-facing or broadly reachable affected services deserve immediate attention. The bundle does not identify default enablement, affected endpoints, or corrected versions.
Exploitation context
The supplied record is not marked as included in CISA KEV and provides no cited evidence of active exploitation. That does not establish that exploitation is absent. The network-accessible, unauthenticated, low-complexity characteristics make vulnerable deployments attractive targets.
Researcher notes
The public bundle establishes the affected range, feature prerequisite, CWE, and CVSS characteristics but does not describe the vulnerable protocol flow, affected endpoints, indicators, or exact fix level. Avoid inferring exploitability for installations where neither feature is enabled. Validate remediation details directly against IBM's advisory.
Mitigation direction
Inventory Liberty versions and identify deployments enabling either affected feature.
Consult IBM advisory 7283488 for exact corrected levels and vendor-approved remediation.
Apply IBM's prescribed update using normal change-control and rollback procedures.
Disable affected features if unnecessary and operationally safe, pending vendor-directed remediation.
Restrict network access to affected services until remediation is verified.
Validation and detection
Confirm each deployment's Liberty version against the affected range.
Inspect configuration for rtcomm-1.0 and rtcommGateway-1.0 enablement.
Verify installed fixes against IBM advisory 7283488.
Retest authentication controls after remediation without attempting exploit reproduction.
Review access logs for unexplained unauthenticated activity around affected services.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.