# CVE-2026-15567: Wildfly: wildfly-iiop: wildfly-jacorb: wildfly: pre-auth denial of service on the iiop listener

> A remote unauthenticated attacker can cause a denial of service in WildFly by triggering an OutOfMemoryError via the IIOP listener.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 22 Oct 2026
- **Also known as:** GHSA-h33j-vrhg-4q7j

## What is CVE-2026-15567?

CVE-2026-15567 is a high-severity denial of service vulnerability in Red Hat Fuse 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

A flaw was found in Wildfly. A remote unauthenticated attacker can trigger OutOfMemoryError as CSIv2Util's GSS token decoder reads an attacker-controlled length field without bounds checking and attempts to allocate a byte array of that size.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

Apply the vendor's patch.

## Is CVE-2026-15567 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15567 is a high-severity denial of service vulnerability in Red Hat Fuse 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-15567 in the wild and no public exploit code.

Affected product: Red Hat Fuse 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-15567/ (Markdown: https://insights.sbomify.com/CVE-2026-15567/index.md)
```

## Sources

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

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