Skip to content
Threat Brief

← All advisories

CVE-2026-114488

High 7.4No known exploitationFix status unknown

Wildfly: wildfly-iiop: wildfly-ejb3: wildfly: authentication bypass on iiop ejb invocations as csiv2 ittprincipalname accepted without transport binding

Record last updated

CVSS score

7.4

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 36% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-829

Patching and mitigation

Patch status
Unknown: no source documents a fix
Mitigation
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.
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
Red HatRed Hat JBoss Enterprise Application Platform 8Not documentedNot documentedCVE Program
Red HatRed Hat Fuse 7 (status unknown)Not documentedNot documentedCVE Program
Red HatRed Hat JBoss Enterprise Application Platform 7 (status unknown)Not documentedNot documentedCVE Program
Red HatRed Hat JBoss Enterprise Application Platform 7 (status unknown)Not documentedNot documentedCVE Program
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack (status unknown)Not documentedNot documentedCVE Program
Red HatRed Hat Single Sign-On 7 (status unknown)Not documentedNot documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by redhat

    Source: CVE Program (opens in a new tab)

Vendor guidance and references