Red Hat JBoss EAP version 5 is vulnerable to a deserialization of untrusted data in the JMX endpoint when deserializes the credentials pass…

published 2018-03-09 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10391

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

Red Hat JBoss EAP version 5 is vulnerable to a deserialization of untrusted data in the JMX endpoint when deserializes the credentials passed to it. An attacker could exploit this vulnerability resulting in a denial of service attack.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-9585 updated 2026-11-07 cvss 5.3

EAP-5: unsafe deserialization of user credentials by the JMX endpoint

Red Hat JBoss Enterprise Application Platform 5 jbossas jbossas Red Hat JBoss SOA Platform 5 jbossas jbossas
affected: workaround, no fix planned “You should not expose Remote JMX on EAP 5, or SOA-P 5. To do that remove this system property from bin/run.conf, or bin/run.conf.bat: com.sun.management.jmxremote.port=<portNum>”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.3	CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD	2.0	2.6	AV:N/AC:H/Au:N/C:N/I:N/A:P

Affected products

Red Hat, Inc. EAP-5

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

bugzilla.redhat.com /show_bug.cgi?id=1404528
issue-tracking
securityfocus.com /bid/94932
vdb-entry, third-party-advisory

Sources

CVE List CVE-2016-9585
NVD CVE-2016-9585

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary