Excessive Platform Resource Consumption within a Loop Affecting eap8-ironjacamar-common-api package, versions <0:3.1.1-1.Final_redhat_00001.1.el9eap


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.53% (45th 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-EAP8IRONJACAMARCOMMONAPI-22499216
  • published12 Nov 2026
  • disclosed23 Sept 2026

Introduced: 23 Sep 2026

CVE-2026-89425  (opens in a new tab)
CWE-1050  (opens in a new tab)

How to fix?

Upgrade RHEL:9 eap8-ironjacamar-common-api to version 0:3.1.1-1.Final_redhat_00001.1.el9eap or higher.
This issue was patched in RHSA-2026:99018.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap8-ironjacamar-common-api package and not the eap8-ironjacamar-common-api package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

UTF8DataInputJsonParser._reportInvalidToken() in FasterXML jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound. Unlike the three sibling parser implementations, including UTF8StreamJsonParser, it never consults ErrorReportConfiguration.getMaxErrorTokenLength() (default 256). A malformed token supplied to a parser created through JsonFactory.createParser(DataInput) is therefore accumulated in full. No StreamReadConstraints setting mitigates this: maxDocumentLength cannot be applied to DataInput sources at all, and maxStringLength does not cover this path because the accumulation bypasses ReadConstrainedTextBuffer. The reporter measured a 20,000,109-character exception message from a 20-million-character malformed token on the DataInput path, against 367 characters for identical input on the InputStream path. Scaling the payload drives the StringBuilder, which also incurs byte-to-char expansion and internal array doubling, to many times the raw payload size and can trigger OutOfMemoryError for the whole JVM. UTF8DataInputJsonParser was introduced in 2.8.0 together with createParser(DataInput); releases before 2.8.0 do not contain the affected class.

CVSS Base Scores

version 3.1