Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed CXF FIQL search endpoint
-
DeliveryCraft long operator-less query string
-
ExploitSubmit request to parser
-
ExecutionTrigger excessive CPU-bound matching
-
ImpactExhaust server resources / degrade service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the target application to use Apache CXF's JAX-RS search extension with the FIQL query parser processing attacker-influenced query input (e.g., a search/filter endpoint accepting FIQL expressions). The trigger is a sufficiently long query string containing no recognizable operator, which drives the operator-search logic into excessive backtracking. LIMITING FACTORS: applications that do not expose FIQL/search query parsing are unaffected; and after the fix, FIQL expressions are capped at 4 KiB by default, so patched or input-size-limited deployments neutralize the long-input vector. No authentication requirement is confirmable from available data (no CVSS vector provided), so auth dependence cannot be asserted. |
| Impact | This is an availability-only denial-of-service issue in Apache CXF's FIQL query parser, where a crafted query string lacking an operator forces the parser into excessive combinatorial searching (algorithmic-complexity / ReDoS-style CPU exhaustion). NO CVSS vector, CWE, EPSS score, KEV listing, or POC was provided in the input, so quantitative exploitation-likelihood signals are entirely absent - risk must be reasoned from the description alone. The flaw is 'no public exploit identified at time of analysis' and is NOT in CISA KEV, so there is no evidence of active exploitation. On its face the issue is remotely triggerable with a single crafted request and low complexity, which argues for meaningful risk, but it is strongly gated by a deployment prerequisite: the target application must actually expose CXF's JAX-RS search/FIQL functionality to attacker-controlled input. The impact ceiling is service degradation/outage, not code execution or data exposure. Net: a real but moderate, availability-scoped priority for the subset of CXF deployments using FIQL search - not a widespread drop-everything event. Note a metadata conflict: the input tags this as 'Information Disclosure,' which contradicts the description (pure CPU-exhaustion DoS); treat the confidentiality framing as mislabeled. |
| Exploit ScenarioDerived | An attacker identifies a CXF-based JAX-RS endpoint that accepts FIQL search expressions and submits a single crafted query containing a very long string with no valid operator. The parser burns excessive CPU attempting operator-match combinations, and repeating such requests exhausts server CPU, slowing or halting legitimate request processing. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
CPU exhaustion denial of service in Apache CXF's FIQL query parser allows remote attackers to degrade or stall a server by submitting a long search expression containing no recognizable operator, which drives the parser's operator-search logic into excessive combinatorial matching and burns CPU on a request-handling thread. Affected are CXF 3.6.x, 4.1.x and 4.2.x deployments that expose FIQL-based search/filter endpoints; the assessed CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (base 7.5), meaning availability impact only, with confidentiality and integrity unaffected. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor-released fixes - 4.2.4, 4.1.9 and 3.6.13 - neutralize the long-input vector by capping FIQL expressions at 4 KiB by default while still permitting normal queries.
RemediationAI
Upgrade to the vendor-released patch versions: Apache CXF 4.2.4, 4.1.9 or 3.6.13 depending on your maintenance branch, as directed by the advisory at https://lists.apache.org/thread.html/mv5qfmd27gkbvt3k6by9db5bolrsbgy1; these releases impose a 4 KiB default cap on FIQL expressions, so long inputs are rejected before the operator-search logic can be driven into combinatorial backtracking. If immediate upgrade is not possible, the most direct compensating control is to enforce your own input-length limit of roughly 4 KiB (matching the new default) on query strings or the specific search/filter parameters that feed the FIQL parser, applied at a reverse proxy, API gateway, WAF or servlet filter - the trade-off is that any legitimately longer search expressions will be rejected until callers are adjusted, so tune the threshold against real query sizes and remember to cap both query parameters and request bodies (JSON/XML filters) that can carry the expression. Where FIQL search is not a required feature, disabling the JAX-RS search extension or not registering the FIQL query parser removes the attack surface entirely, with the side effect that existing search/filter functionality stops working; additionally, rate-limiting and request-timeout settings on the affected endpoints can bound the CPU spent per client and blunt the impact, though they do not eliminate the underlying vulnerability and must be sized carefully to avoid cutting off legitimate traffic or long-running legitimate requests.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache CXF's JAX-RS search extension (the org.apache.cxf.jaxrs.ext.search FIQL support) implements Feed Item Query Language, translating expressions such as 'name==foo;age=gt=30' into an internal SearchCondition tree that is then applied as a filter over JAX-RS resources. To build that tree the parser must locate operator tokens within the raw query string; the vulnerable implementation scans for those operators with a pattern that explores many candidate combinations, so a sufficiently long input that contains no valid operator never terminates quickly and instead degenerates into excessive backtracking/combinatorial searching - the algorithmic-complexity (ReDoS-style) class of resource-consumption bug. The practical consequence is uncontrolled CPU consumption on the parsing thread, which in thread-per-request servlet containers consumes a worker thread and can cascade into request-queue saturation and apparent service unavailability; because the work is done during request parsing, it occurs before any application-level authorization or business logic. The supplied CPE string cpe:2.3:a:apache_software_foundation:apache_cxf:*:*:*:*:*:*:*:* is version-wildcarded, consistent with the vendor's remediation of three maintenance branches (3.6.x, 4.1.x, 4.2.x) rather than a single product edition; the CVE carries no CWE assignment in the input data, though the behaviour maps to the inefficient-regular-expression-complexity / uncontrolled-resource-consumption family. Exposure is bounded by deployment: applications that do not mount FIQL/search query parsing are not reachable through this vector.
Know when Apache Cxf gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Remotely reachable parser (AV:N) triggered by a single crafted query (AC:L, no UI); FIQL endpoints are typically unauthenticated (PR:N); impact is CPU-exhaustion DoS only, so C:N/I:N/A:H.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
2DescriptionCVE.org
Apache CXF's FIQL query parser has a vulnerability in how it searches for operators in query expressions. The search pattern can get stuck trying many combinations when it encounters a long string without an operator, causing the parser to consume excessive CPU time. An attacker can send a crafted query to make the server use up CPU resources, potentially slowing down or stopping other requests. The fix was to limit FIQL expressions to 4 KiB by default, preventing attackers from sending extremely long inputs while still allowing normal queries.
Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Apache Cxf
View allArbitrary certificate disclosure in Apache CXF's XKMS server lets remote attackers abuse an LDAP injection flaw (CWE-90)
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination t
Token validation bypass in Apache CXF's STSTokenValidator and Security Token Service (STS) allows unauthenticated remote
Man-in-the-middle attackers can impersonate any TLS server contacted by Apache CXF's optional Netty-based HTTP client tr
XML signature wrapping in Apache CXF's JAX-RS XML Security module allows remote, unauthenticated attackers to have unsig
Trust bypass in Apache CXF's STSTokenValidator allows a remote, unauthenticated attacker to have a forged SAML assertion
A remote, unauthenticated attacker can exhaust server heap memory in Apache CXF by submitting a small (kilobyte-scale) D
Remote code execution in Apache CXF (versions before 3.6.11, 4.0.0-4.1.5, and 4.2.0) arises because the fix for CVE-2025
XML External Entity injection in Apache CXF's WSDL import processing allows attackers who can influence imported WSDL or
Denial of service persists in Apache CXF due to an incomplete remediation of CVE-2026-50645, allowing unauthenticated ne
Authorization scope escalation in Apache CXF's OAuth2 Dynamic Client Registration endpoint allows any registering client
Open redirect in Apache CXF's OIDC relying-party component lets remote, unauthenticated attackers steer users to an atta
EUVD-2026-95698
GHSA-ppm6-prq5-wv37
NVD
CVE.org
EPSS
VulDB
Exploit-DB