VulnerabilityPublished 6 Nov 2026

CVE-2026-121837: Red Hat Exploit Intelligence · Incorrect Authorization

Affects Red Hat Exploit IntelligenceSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 6 Nov 2026, 05:54 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Exploit Intelligenceexploit-intelligence/agent-client-rhel9	Affected–	Fixed in–
Red Hat build of Quarkusquarkus-rest-data-panache	Affected–	Fixed in–

AI-suggested

Red Hat has published an advisory but does not explicitly state a patch or fix availability in the provided content. Until a fix is applied, ensure that security constraints are applied directly to entity fields rather than getter methods to avoid bypass. Review application configurations to restrict access to REST endpoints requiring authentication to reduce exposure.

Description

CVE-2026-121837 is a vulnerability in the REST Data Panache component of Quarkus used by Red Hat Exploit Intelligence. It occurs when a security constraint is applied via the @SecureField annotation on a getter method instead of the field itself, causing the generated REST resource to improperly enforce filtering and sorting restrictions. This flaw allows authenticated users to infer sensitive data values by analyzing which records match filter criteria or their order, even though the sensitive values are not directly exposed in responses.

Impact

An authenticated attacker can bypass intended access controls on entity properties secured via @SecureField on getter methods, allowing inference of sensitive data values through side-channel analysis of filtering and sorting results. The vulnerability does not expose the data directly but leaks information by how records match filter criteria or their order. There is no impact on data integrity or availability. The attack vector is network-based with low complexity and no user interaction required.

Summary

This vulnerability arises from the REST Data Panache resource generator in Quarkus failing to consider @SecureField annotations placed on getter methods when constructing query logic for filtering and sorting. As a result, security constraints intended to restrict access to sensitive entity properties are bypassed during these operations. An authenticated attacker can exploit this to infer sensitive data values indirectly by observing filtering and sorting behavior, despite the values being omitted from the final REST response. The issue is classified under CWE-863 (Incorrect Authorization). Red Hat has assessed the severity as moderate, with a CVSS 3.1 base score of 4.3, reflecting low confidentiality impact and no integrity or availability impact. Exploitation requires authenticated access to the REST endpoint, which may depend on application configuration.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 05:54 UTC

Technical details

References

Community reviews

Related threats