CVE-2026-114488

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

  • High 7.4

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.

Key facts

Published
29 Oct 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.406% likely to be exploited in the next 30 days, higher than 35.375% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.4CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • 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 tempCNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat JBoss Enterprise Application Platform 8.1
  • Default status: unaffected
Red HatRed Hat Fuse 7
  • Default status: unknown
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unknown
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unknown
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: unknown

Timeline

  1. 23 Jun 2026 Reported to Red Hat.
  2. 27 Oct 2026 Made public.
  3. 29 Oct 2026 Published

Weakness

References