Description
A flaw was found in Wildfly. A remote attacker can bypass authentication on IIOP EJB invocations as the CSIv2 security interceptor accepts ITTPrincipalName identity assertions in the service context without verifying transport-level authentication, allowing a pre-auth attacker on the port 3528 to impersonate any principal on every IIOP-exposed @Remote EJB.
Published: 2026-10-29
Score: 7.4 High
EPSS: n/a
KEV: No
Impact: Authentication Bypass
Action: Apply Workaround
AI Analysis

Impact

Wildfly contains an authentication bypass flaw in the IIOP subsystem. An unauthenticated remote attacker who can reach the IIOP port 3528 may supply an ITTPrincipalName in the service context. The CSIv2 security interceptor does not verify transport-level authentication, so the attacker’s supplied principal is accepted, enabling impersonation of any remote EJB principal on @Remote EJBs. This grants the attacker full authentication and access rights that belong to the impersonated principal, exposing the confidentiality, integrity, and availability of the affected services.

Affected Systems

Affected by this issue are Red Hat Fuse 7, Red Hat JBoss Enterprise Application Platform 7, Red Hat JBoss Enterprise Application Platform 8, the Red Hat JBoss Enterprise Application Platform Expansion Pack, and Red Hat Single Sign‑On 7. The advisory does not list specific JPES versions, so any installation of these products using Wildfly with the IIOP branch is potentially vulnerable until a patch is applied.

Risk and Exploitability

The CVSS score of 7.4 indicates a high‑severity vulnerability, and although an EPSS score is not available, the flaw permits unauthenticated remote control via a well‑known TCP port, making exploitation straightforward. The vulnerability is not listed in CISA’s KEV catalog, but the attack surface—port 3528—is exposed over the network and the logic flaw does not require special credentials. An attacker capable of reaching the IIOP interface could bypass authentication and impersonate any user; therefore the likelihood of exploitation is high if the IIOP port remains open to untrusted hosts.

Generated by OpenCVE AI on October 29, 2026 at 07:21 UTC.

Remediation

Vendor Workaround

To mitigate this vulnerability without modifying binaries, apply one or more of the following operational and configuration controls: 1. Maintain or revert caller propagation to the default 'none' setting in the IIOP subsystem configuration: Run the following management CLI command: `/subsystem=iiop-openjdk:write-attribute(name=caller-propagation,value=none)` Ensure that application deployment descriptors (such as jboss-ejb3.xml) do not explicitly override caller propagation to 'supported'. 2. Restrict network reachability: Block external access to the CORBA/IIOP port (default TCP port 3528) using firewall rules, or restrict access strictly to trusted application networks: `firewall-cmd --remove-port=3528/tcp --permanent && firewall-cmd --reload` 3. Enforce transport-level security: If caller propagation is required for your architecture, configure the IIOP subsystem to require SSL/TLS with client certificate authentication by setting `server-requires-ssl="true"`, or enforce mandatory authentication via the `as-context` configuration. Caveats: Disabling caller propagation prevents client security identity forwarding across remote IIOP EJB calls, which may impact applications relying on distributed identity propagation. Restricting firewall access will prevent external clients outside authorized networks from connecting to IIOP services. Warning: Applying configuration changes via the JBoss management CLI requires reloading the runtime service (`:reload`), which will temporarily interrupt active client connections.


OpenCVE Recommended Actions

  • Reconfigure the IIOP subsystem to set caller‑propagation to "none", preventing client identity forwarding across remote IIOP EJB calls.
  • Block or restrict inbound traffic on TCP port 3528 using firewall rules so that only trusted networks can reach the IIOP interface.
  • If caller propagation cannot be disabled, require SSL/TLS with client‑certificate authentication by setting server‑requires‑ssl="true" or enforce mandatory authentication via the as-context configuration.

Generated by OpenCVE AI on October 29, 2026 at 07:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 29 Oct 2026 06:15:00 +0000

Type Values Removed Values Added
Description A flaw was found in Wildfly. A remote attacker can bypass authentication on IIOP EJB invocations as the CSIv2 security interceptor accepts ITTPrincipalName identity assertions in the service context without verifying transport-level authentication, allowing a pre-auth attacker on the port 3528 to impersonate any principal on every IIOP-exposed @Remote EJB.
Title Wildfly: wildfly-iiop: wildfly-ejb3: wildfly: authentication bypass on iiop ejb invocations as csiv2 ittprincipalname accepted without transport binding
First Time appeared Redhat
Redhat jboss Enterprise Application Platform
Redhat jboss Fuse
Redhat jbosseapxp
Redhat red Hat Single Sign On
Weaknesses CWE-829
CPEs cpe:/a:redhat:jboss_enterprise_application_platform:7
cpe:/a:redhat:jboss_enterprise_application_platform:8
cpe:/a:redhat:jboss_fuse:7
cpe:/a:redhat:jbosseapxp
cpe:/a:redhat:red_hat_single_sign_on:7
Vendors & Products Redhat
Redhat jboss Enterprise Application Platform
Redhat jboss Fuse
Redhat jbosseapxp
Redhat red Hat Single Sign On
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Redhat Jboss Enterprise Application Platform Jboss Fuse Jbosseapxp Red Hat Single Sign On
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-10-29T06:07:33.732Z

Reserved: 2026-10-21T15:33:52.420Z

Link: CVE-2026-114488

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-29T06:17:19.103

Modified: 2026-10-29T06:17:19.283

Link: CVE-2026-114488

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-29T07:30:14Z

Weaknesses
  • CWE-829

    Inclusion of Functionality from Untrusted Control Sphere