# CVE-2026-86404: Deserialization in Red Hat AMQ Broker 7

> Red Hat JBoss EAP permits unsafe deserialization by default in Artemis messaging, allowing attackers to execute arbitrary code via crafted messages.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Sep 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-q97r-w4hq-94gr

## What is CVE-2026-86404?

CVE-2026-86404 is a high-severity unsafe deserialization vulnerability in Red Hat AMQ Broker 7, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject() uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity()/isTrustedType() method. However, by default both allow-list and block-list are empty. When the allow-list is empty (size == 0), isTrustedType() returns true for ALL classes. This means all classes are deserializable by default.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

Change a configuration setting.

## Is CVE-2026-86404 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86404 is a high-severity unsafe deserialization vulnerability in Red Hat AMQ Broker 7, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86404 in the wild and no public exploit code.

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

## Sources

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

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