# CVE-2026-15563: Wildfly-iiop-openjdk: missing authentication on eap's iiop nameservice leads to mitm or dos

> Attackers can hijack JNDI lookups via unauthenticated IIOP NameService bind operations, enabling man-in-the-middle attacks or denial of service.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-259j-555g-mwrr

## What is CVE-2026-15563?

CVE-2026-15563 is a high-severity missing authorization vulnerability in Red Hat RHEL-8 based Middleware Containers, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in EAP's IIOP. The listener's NameService would accept bind operations without authentication, allowing an attacker to hijack JNDI lookups and binding them to a malicious ORB, achieving MITM or DoS on further invocations.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-15563?


## How do I fix CVE-2026-15563?

Apply the vendor's patch.

## Is CVE-2026-15563 being exploited?

There is no known exploitation of CVE-2026-15563 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15563 and fix it if it is affected.

What it is: CVE-2026-15563 is a high-severity missing authorization vulnerability in Red Hat RHEL-8 based Middleware Containers, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15563 in the wild and no public exploit code.

Affected product: Red Hat RHEL-8 based Middleware Containers. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15563/ (Markdown: https://insights.sbomify.com/CVE-2026-15563/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15563
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15563
- OSV: https://osv.dev/vulnerability/CVE-2026-15563

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15563/
Summaries are generated and may contain mistakes; the official description above is the record.