Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94451 Overview
CVE-2026-94451 affects Quarkus REST Data Panache, a framework extension that automatically generates REST endpoints for data entities. The vulnerability stems from improper input validation [CWE-20] of the sort parameter in generated endpoints. Attackers can supply crafted sort values that reach the underlying data layer without sufficient checks. This can expose information outside the attacker's intended scope or force the database to execute expensive operations. The result is unauthorized data inference or denial of service through resource exhaustion.
Critical Impact
Unauthenticated attackers can abuse the sort parameter to enumerate restricted data or degrade service availability by triggering costly database operations.
Affected Products
- Quarkus REST Data Panache extension
- Red Hat build of Quarkus (per RHSA-2026:83082 and RHSA-2026:83520)
- Applications auto-generating REST endpoints via quarkus-hibernate-orm-rest-data-panache
Discovery Timeline
- 2026-10-12 - CVE-2026-94451 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-94451
Vulnerability Analysis
Quarkus REST Data Panache generates CRUD-style REST endpoints directly from Panache entities. These endpoints accept a sort query parameter to control result ordering. The affected code paths do not fully validate the fields referenced in that parameter. Attackers can pass arbitrary property names or chained expressions that the ORM translates into SQL ORDER BY clauses. By observing response ordering, an attacker can infer values of fields that the API does not expose directly. The same parameter can also reference deeply joined or non-indexed columns that force the database into expensive sort operations, consuming CPU and memory.
Root Cause
The root cause is improper input validation [CWE-20]. The generated endpoints trust client-supplied sort tokens and forward them to the persistence layer without constraining them to an allow-list of safe, exposed fields. See the Red Hat CVE Analysis for CVE-2026-94451 for upstream details.
Attack Vector
Exploitation is remote and unauthenticated against any application that exposes Panache-generated REST endpoints. An attacker issues HTTP GET requests with crafted sort query parameters targeting hidden fields or expensive join columns. Repeated requests allow blind data inference, while concurrent requests referencing high-cost sort expressions cause availability degradation.
No verified public proof-of-concept code is available. See the Red Hat Bug Report #2537516 for technical references.
Detection Methods for CVE-2026-94451
Indicators of Compromise
- HTTP requests to Panache-generated endpoints containing unusual sort parameter values referencing non-UI fields.
- Spikes in slow database queries involving ORDER BY on non-indexed or joined columns.
- Repeated requests from a single source iterating sort fields with small response differences, indicating blind inference.
Detection Strategies
- Enable access logging on Quarkus applications and alert on sort= parameters referencing fields outside an approved allow-list.
- Correlate web access logs with database slow-query logs to identify sort-driven resource exhaustion.
- Deploy WAF rules that reject sort values containing dots, commas, or field names not present in the published API schema.
Monitoring Recommendations
- Track p95 and p99 latency on REST Data Panache endpoints and alert on sustained increases tied to specific query parameters.
- Monitor database CPU and I/O for sort-heavy workloads originating from the Quarkus service account.
- Record and review query parameter cardinality to surface enumeration patterns against the sort field.
How to Mitigate CVE-2026-94451
Immediate Actions Required
- Apply the fixes shipped in RHSA-2026:83082 and RHSA-2026:83520 to all affected Quarkus deployments.
- Inventory applications using quarkus-hibernate-orm-rest-data-panache and confirm which generated endpoints accept the sort parameter.
- Restrict exposure of auto-generated endpoints at the gateway or ingress layer until patches are deployed.
Patch Information
Red Hat has issued patched builds via RHSA-2026:83082 and RHSA-2026:83520. Upgrade the Quarkus REST Data Panache extension to the fixed version referenced in the Red Hat CVE Analysis for CVE-2026-94451. Rebuild and redeploy affected applications after upgrading.
Workarounds
- Override generated resource methods to validate the sort parameter against a strict allow-list of exposed fields before passing it to Panache.
- Disable auto-generated endpoints for sensitive entities and expose only hand-written resources with explicit sort validation.
- Place a reverse proxy or WAF rule in front of affected services that strips or rejects unknown sort field names.
# Example WAF rule concept to allow-list sort fields
# Reject requests whose sort parameter is not in an approved set
if ($arg_sort !~* "^(id|name|createdAt|updatedAt)(,(asc|desc))?$") {
return 400;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

