CVE-2026-119542

Org.infinispan/infinispan-query: infinispan: deeply nested ickle queries can trigger a stackoverflowerror

  • Medium 4.3

Description

A flaw was found in the Ickle query parser in Infinispan. A query containing deeply nested predicates can cause recursive parsing to exhaust the Java thread stack and throw an uncaught StackOverflowError. An authenticated user with BULK_READ permission who can submit a cache query may trigger the issue, potentially affecting availability.

Key facts

Published
30 Oct 2026
Last changed
30 Oct 2026
Assigned by
redhat
EPSS
0.332% likely to be exploited in the next 30 days, higher than 26.774% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 4.3CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat build of Apache Camel 4 for Quarkus 3
  • Default status: affected
Red HatRed Hat Data Grid 8
  • Default status: affected
Red HatRed Hat Fuse 7
  • Default status: unknown
Red HatRed Hat JBoss Enterprise Application Platform 8
  • Default status: affected
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack
  • Default status: affected

Timeline

  1. 16 Oct 2026 Reported to Red Hat.
  2. 30 Oct 2026 Made public.
  3. 30 Oct 2026 Published

Weakness

References