PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-89238 – Encryption Policy Bypass / Confidentiality Bypass – Apache WSS4J < 4.0.2, < 3.0.6,

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-89238 is a critical vulnerability in Apache WSS4J, the widely-used Java library implementing WS-Security for SOAP web services, caused by "EncryptedHeader child confusion" during decryption processing. The flaw allows an attacker to cause an attacker-controlled plaintext XML element to be treated by WSS4J as the legitimately decrypted header, letting forged content masquerade as protected data and bypass WS-SecurityPolicy confidentiality enforcement. It carries a CVSS v3.1 base score of 9.1 (Critical) and affects a broad range of WSS4J versions used across SOAP-based enterprise and government web services.

Technical details

  • Root cause: WSS4J’s handling of <wsse:EncryptedHeader> elements does not properly verify which child element within the encrypted header structure is the genuine decrypted content, allowing "child confusion" between the real decrypted node and an attacker-supplied plaintext node (CWE-345: Insufficient Verification of Data Authenticity).
  • Trigger conditions: An attacker able to submit or intercept/modify a SOAP message processed by a vulnerable WSS4J consumer can insert a crafted plaintext element inside an EncryptedHeader wrapper so that WSS4J selects it as if it had been decrypted.
  • Attack vector: Network-exploitable (AV:N); no authentication or user interaction is required to submit a malicious SOAP request to an endpoint that processes WS-Security encrypted headers.
  • Impact: Successful exploitation results in "wrong protected-header selection," which can bypass WS-SecurityPolicy confidentiality assurances and allow attacker-controlled data to be trusted as if it were confidentiality-protected, undermining message integrity guarantees tied to that header content. The CVSS vector reflects high confidentiality and integrity impact with no availability impact.

Affected software

  • Apache WSS4J (org.apache.wss4j:wss4j-ws-security-dom) versions 4.0.0 to before 4.0.2
  • Apache WSS4J versions 3.0.0 to before 3.0.6
  • Apache WSS4J versions before 2.4.4 (all 2.x releases)

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Apache WSS4J to the patched releases:
    • 4.0.2 (for the 4.0.x line)
    • 3.0.6 (for the 3.0.x line)
    • 2.4.4 (for all 2.x lines)
  • If immediate patching is not possible: No official workaround has been published by the Apache Software Foundation beyond upgrading; organizations should restrict network exposure of SOAP/WS-Security endpoints that rely on WSS4J for header encryption enforcement and monitor for malformed or unexpected EncryptedHeader structures until the upgrade can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge