# CVE-2016-4978: Apache ActiveMQ Artemis RCE Via Deserialization Gadget Chain

> Remote authenticated users can execute arbitrary code via unsafe deserialization in Apache ActiveMQ Artemis message handling.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r9vv-xj4w-g8m8

## What is CVE-2016-4978?

CVE-2016-4978 is a high-severity unsafe deserialization vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Sep 2016. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The getObject method of the javax.jms.ObjectMessage class in the (1) JMS Core client, (2) Artemis broker, and (3) Artemis REST component in Apache ActiveMQ Artemis before 1.4.0 might allow remote authenticated users with permission to send messages to the Artemis broker to deserialize arbitrary objects and execute arbitrary code by leveraging gadget classes being present on the Artemis classpath.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2016-4978?

2 open source packages ship an affected version, including org.apache.activemq:artemis-pom. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.activemq:artemis-pom` | Maven | All versions | 1.4.0 |
| `org.apache.activemq:artemis-pom` | Maven | All versions | 1.4.0 |

Products: Apache Artemis, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2016-4978?

Upgrade org.apache.activemq:artemis-pom to 1.4.0 or later.

## Is CVE-2016-4978 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2026-57967](https://insights.sbomify.com/CVE-2026-57967/): Apache Artemis, Apache ActiveMQ Artemis: Missing authentication on CORE protocol session reattachment (critical 9.8)
- [CVE-2026-27446](https://insights.sbomify.com/CVE-2026-27446/): Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation (critical 9.3)
- [CVE-2026-49364](https://insights.sbomify.com/CVE-2026-49364/): Information disclosure in Apache ActiveMQ Artemis (critical 9.1)
- [CVE-2026-67593](https://insights.sbomify.com/CVE-2026-67593/): Missing authorization in Apache ActiveMQ Artemis (critical 9.1)
- [CVE-2023-50780](https://insights.sbomify.com/CVE-2023-50780/): Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4978 and fix it if it is affected.

What it is: CVE-2016-4978 is a high-severity unsafe deserialization vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Sep 2016. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-4978 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.activemq:artemis-pom (Maven): affected all versions; fixed in 1.4.0
- org.apache.activemq:artemis-pom (Maven): affected all versions; fixed in 1.4.0

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-2016-4978/ (Markdown: https://insights.sbomify.com/CVE-2016-4978/index.md)
```

## Sources

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

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