Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package eap7-ironjacamar-core-api  (opens in a new tab)


Threat Intelligence

EPSS
0.7% (54th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-EAP7IRONJACAMARCOREAPI-19949768
  • published19 Sept 2026
  • disclosed11 Aug 2026

Introduced: 11 Aug 2026

CVE-2026-86404  (opens in a new tab)
CWE-502  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap7-ironjacamar-core-api package and not the eap7-ironjacamar-core-api package as distributed by RHEL.

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.