# CVE-2026-15562: Jboss-remoting: jboss-remoting: integer overflow in messagereader leads to pre-authentication denial of service

> Remote unauthenticated attackers can cause server-wide denial of service via integer overflow in JBoss Remoting message reader.

- **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:** 20 Oct 2026
- **Also known as:** GHSA-r89v-33gc-39f6

## What is CVE-2026-15562?

CVE-2026-15562 is a high-severity 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

A flaw was found in EAP's jboss-remoting. A remote unauthenticated attacker who can reach :8080 (or :9990, or :4447) and complete an Upgrade: jboss-remoting handshake can cause OOM errors that degrade requests server-wide, leading to denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-15562 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15562 is a high-severity 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-15562 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-15562/ (Markdown: https://insights.sbomify.com/CVE-2026-15562/index.md)
```

## Sources

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

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