CVE-2026-15564

Wildfly-ejb: wildfly-iiop-openjdk: eap iiop listeners may permit unauthed deserialization

  • High 7.4

Description

Wildfly's IIOP listener may permit deserialization of input streams before authentication is performed. An attacker who can gain access to the IIOP port may be able to construct and send malicious objects and achieve deserialization, if the target EJB allows untyped method parameters, and depending on the potential gadget chains available in the running classpath.

Key facts

Published
29 Oct 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.141% likely to be exploited in the next 30 days, higher than 3.495% 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:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do

  • Restrict network reachability to the IIOP listener (default TCP port 3528) so that only localhost or authorized management networks can access it. 1. Restrict port exposure using firewalld: ```bash firewall-cmd --permanent --remove-port=3528/tcp firewall-cmd --reload ``` 2. If CORBA/IIOP interoperability is not required by deployed applications, remove the IIOP subsystem using the JBoss Management CLI: ```bash jboss-cli.sh --connect --command="/subsystem=iiop-openjdk:remove" ``` Caveats: Removing the IIOP subsystem will break remote EJB invocations or external services that rely on CORBA/IIOP protocols. Warning: Applying firewall changes or removing server subsystems will disrupt active client connections and requires reloading the server configuration or restarting the JBoss EAP service to take full effect.CNA 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.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat JBoss Enterprise Application Platform 8.1
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: affected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 8
  • Default status: affected

Timeline

  1. 15 May 2026 Reported to Red Hat.
  2. 27 Oct 2026 Made public.
  3. 29 Oct 2026 Published

Weakness

References