Keycloak on Red Hat direct request

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.3$0-$5k2.66-

Summaryinfo

A vulnerability, which was classified as problematic, was found in Keycloak on Red Hat. The affected element is an unknown function. Such manipulation leads to direct request. This vulnerability is uniquely identified as CVE-2026-11986. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Keycloak on Red Hat (affected version not known). Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a direct request vulnerability. Using CWE to declare the problem leads to CWE-425. The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files. Impacted is integrity, and availability.

The advisory is available at access.redhat.com. This vulnerability is handled as CVE-2026-11986 since 06/11/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/11/2026). This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3

VulDB Base Score: 3.8
VulDB Temp Score: 3.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 4.9
CNA Vector (redhat): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Direct request
CWE: CWE-425
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

06/11/2026 Advisory disclosed
06/11/2026 +0 days CVE reserved
06/11/2026 +0 days VulDB entry created
06/11/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: access.redhat.com
Status: Confirmed

CVE: CVE-2026-11986 (🔒)
GCVE (CVE): GCVE-0-2026-11986
GCVE (VulDB): GCVE-100-370442

Entryinfo

Created: 06/11/2026 22:39
Changes: 06/11/2026 22:39 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!