# CVE-2026-15560: Openjdk-orb: unauthed class loading via iiop in eap

> Unauthenticated attackers can execute arbitrary code in JBoss EAP by supplying malicious CDR codebase URLs during IIOP object unmarshalling when security manager is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-4238-grjh-g4xm

## What is CVE-2026-15560?

CVE-2026-15560 is a high-severity unsafe deserialization vulnerability in Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

when EAP runs with -secmgr, the openjdk-orb's JDKBridge honours attacker-supplied CDR codebase URLs during object unmarshalling on :3528, allowing an unauthenticated attacker to load and instantiate arbitrary classes from a remote URL in the server JVM before EJB security interceptors run.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

Apply the vendor's patch.

## Is CVE-2026-15560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15560 is a high-severity unsafe deserialization vulnerability in Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7, 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-15560 in the wild and no public exploit code.

Affected product: Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7. 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-15560/ (Markdown: https://insights.sbomify.com/CVE-2026-15560/index.md)
```

## Sources

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

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