Bug 2566744 (CVE-2026-121837) - CVE-2026-121837 quarkus-rest-data-panache: quarkus-rest-data-panache: getter-level @SecureField ignored for filter and sort
Summary: CVE-2026-121837 quarkus-rest-data-panache: quarkus-rest-data-panache: getter-...
Keywords:
Status: NEW
Alias: CVE-2026-121837
Deadline: 2026-12-31
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-04 07:00 UTC by OSIDB Bzimport
Modified: 2026-11-05 09:43 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-04 07:00:55 UTC
A vulnerability was found in io.quarkus:quarkus-rest-data-panache where getter-level @SecureField annotations are ignored during the generation of filter and sort logic for REST Data Panache resources. When @SecureField(rolesAllowed = ...) is placed on a property getter, the generated list endpoint does not check for the required roles when processing filter (?field=value) or sort (?sort=field) parameters.
While the sensitive values are correctly masked in the resulting JSON response, an attacker with access to the endpoint can perform the following actions:
Determine if any records match a specific sensitive value by using filter parameters.

Determine the relative ordering of records based on the sensitive field using sort parameters.

Systematically infer sensitive values through repeated targeted filtering.


This issue only affects @SecureField when placed on the getter; placing the annotation directly on the field is not affected.


Note You need to log in before you can comment on or make changes to this bug.