# CVE-2026-15555: Deserialization in Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7

> Attackers can achieve remote code execution on cluster nodes by exploiting unfiltered deserialization in the Infinispan session replication path.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-8qrr-8665-54fg

## What is CVE-2026-15555?

CVE-2026-15555 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. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in JBoss marshalling. The Infinispan session replication path deserializes replicated session data via the JBoss Marshalling River unmarshaller with no class filtering — enabling RCE via deserialization gadget chains on every cluster node.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

Apply the vendor's patch.

## Is CVE-2026-15555 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15555 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. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15555 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-15555/ (Markdown: https://insights.sbomify.com/CVE-2026-15555/index.md)
```

## Sources

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

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