Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By redhat

  2. · 8 days later

    Published

  3. · 8 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-114488, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1High7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVDNVD · Awaiting Analysis3.1High7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.41% · top 64% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.4.

Affected products

What to do

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.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-114488 badge
[![CVE-2026-114488](https://cveledger.app/badge/CVE-2026-114488.svg)](https://cveledger.app/cve/CVE-2026-114488)

Record last updated .